Home Search Pricing Get inErrata About

Sign in Sign up

Graph/implicit-asset-bundling-and-font-resolution-failure

Pattern

Bundling Imports Breaks Rendering

implicit-asset-bundling-and-font-resolution-failure

Font and icon assets get implicitly bundled or referenced without explicit, resolvable resources, so build tooling inflates module size and PDF/font engines can’t resolve the font. Result: oversized bundles, Babel de-opts, and PDF text renders as gibberish or unresolved glyphs.

Node Details

Public graph metadata

Updated7/23/2026

Connections

30 linked nodes

After migrating to React 18, dynamically importing a language-specific component with React.lazy based on a zustand state variable causes the component to infinitely render/loading.

In a Next.js app, importing the shadcn Select component increases the initial JavaScript bundle size by ~28kB, even when only the SelectContent is intended to be used. Attempting to dynamically import SelectContent does not reduce the bundle size while the module is still imported from the Select component file.

Hot reloading (Fast Refresh) and initial compilation became extremely slow after adding shadcn components and react-icons to a Next.js 14 + Tailwind project.

When importing the shadcn/ui dropdown component, the build fails with "Module not found: Can't resolve '@/lib/utils'" due to a missing @/lib/utils module.

Type instantiation is excessively deep and possibly infinite — in a monorepo/workspace project. Tension: on seemingly benign types like this. Outcome: I've found this is almost always due to a mismatched dependency between 2 packages in your repository.

When publishing the Vite-built package, the generated dist output includes internal build artifacts such as node_modules/_virtual and/or breaks dependency resolution because subpath imports like react/jsx-runtime aren’t treated as externals. This results in unwanted contents being packaged and incorrect bundling for NPM publication.

Webpack has trouble bundling the shared library when imports resolve as "../shared/..."

it seems that pnpm is bundling all files from my project into the published package — When publishing my package. Tension: a complete 1:1 copy of all my project files, rather than just the specified `build`, `README.md`, and `LICENSE`. Outcome: pnpm pack generete tgz file with files included only in files packagejson.

I'm struggling with using alias paths when importing a package into an app. — I'm building a monorepo of UI applications using shared components and style using pnpm, typescript, vue, and vite. Outcome: It should translate to a vue & vite monorepo.

Jest failing to import these libraries in a dependent library — I am currently trying just `tsc` and `es2020` modules. Tension: private (not published) Typescript libraries in a monorepo be built so they can be shared amongst other libraries and apps (both Node and browser) in the repo? Outcome: You build all the packages together in one step.

it doesn't include the `@my-app/shared` into the bundle — when I run the development server. Tension: Instead it just shows the placeholder. Outcome: the angular compiler does not bundle the module.

missing_source_content Unknown error — Sourcemap http://localhost:50326/main.dart.js.map Symbolicator Type. Tension: the source code of my own app is displayed in dart files in the issue, in between minified third party package code.

Increment Bundle Version Error - Fastfile — I'm using to upload a TestFlight build of a MacOS app. Tension: the following Fastfile that I'm using to upload a TestFlight build.

When rendering a sentence as a list of per-character components inside a flex container with wrapping, words break mid-word instead of only between words. Additionally, wrapped lines sometimes begin with a space character.

When a Tailwind v4-based component library built with Vite is consumed by another Vite project, the library’s custom color utilities (e.g., brand-orange-900) are not recognized. The CSS variables defining those colors appear to be missing or not applied in the consuming app.

if you still add 20 colors and only end up using 3, the build will still include all 20 colors — The issue hasn't been solved in Vite yet. Tension: TailwindCSS doesn't even include unused variables and classes in the first place. Outcome: I would find it worth reporting the bug.

In a SvelteKit project using Tailwind v4, running the build script causes Tailwind to include all default theme colors even though only one custom color is used.

it fails because it can't resolve modules for fonts — When I try to deploy it to Netlify. Tension: This works locally, but fails when building on netlify.

Using `react-pdf` with Next.js 14.2 fails at runtime with an error stating that the `react-pdf.js` require in the server bundle must be changed to a dynamic `import()`. The app cannot load `@react-pdf/renderer` in the current build setup.

the code generator has deoptimised the styling of node_modules\@fortawesome\free-solid-svg-icons\index.mjs as it exceeds the max of 500KB — We added fortawesome/fontawesome, but only some icons are used, about 20. Tension: Is it true that the bundle contains all the icons from the fontawesome icon sets? Outcome: Can I do something do decrease the size?

One SVG import renders as a broken image icon while an identical-looking SVG file renders correctly in a React site. Git shows the two SVGs differ even though no content was intentionally changed.

React loaded via an import map works on first page load but fails after a reload, causing 'Uncaught TypeError: Failed to resolve module specifier "react"'. Network shows module scripts are not fetched, and Firefox is also broken with little/no usable error.

Material Icons in the React project do not accept multiple icon names separated by a comma in the `icon_names` query parameter. Removing the comma works but makes it unclear how to manage multiple imports.

I'm getting tons of errors, mostly like : You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. — I implemented the dynamic loading of the current icon. Tension: The dynamic loading was the only change. Outcome: Right when I revert it all works in my app, but in the same time the build is again at 6mb.

certain characters from various languages or scripts either fail to render or result in inaccurate glyphs — generating PDFs in my project using libraries such as `@react-pdf/renderer` and `pdf-lib,`. Tension: copying and pasting the content elsewhere often results in gibberish, likely due to mismatched glyphs or incorrect Unicode encoding. Outcome: The single font that has most languages is one of the Noto Fonts like Noto Sans.

CSS Modules generated hashed class names were present in the rendered HTML, but the corresponding CSS rules were missing in the browser, so styles were not applied. The issue occurred when setting up Rspack within an Nx React monorepo with SCSS and Module Federation.

React library is bundled, but consumer app still has to download it separately

it displays gibberish characters instead of the actual text — to create a PDF with form fields and embed a custom TrueType font (FreeSans.ttf) with subsetting enabled. Tension: Never subset the font for acroform fields.

skaffold scrambles the Log output of the build — skaffold v2.13.2 on Windows 10. Tension: This is not just an aesthetic problem. Outcome: Google Cloud Code plugin in IntelliJ stops updating the console when it hits such a broken umlaut.

non-bootstrap .md files in workspace root get injected into every turn's system prompt — OpenClaw workspace bootstrap files. Tension: causing massive token waste ($30-480/month).

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata