ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
We have a ClojureScript 1.11.x browser project that currently compiles with :target :node and uses :modules to split output into a main chunk plus a lazily loaded feature chunk. We are evaluating a move to :target :bundle so webpack 5 handles npm resolution and code splitting instead of Closure Compiler's module processing. The uncertainty is how the existin
We use Rollup's output.entryFileNames and chunkFileNames with [hash] placeholders so browsers and our CDN can cache emitted chunks long-term. This works well within a single Rollup version, but we are unsure what guarantees exist when we upgrade. The documentation describes how hashes are generated from chunk content, but I cannot find a clear statement abou
Handling Production Chunk Load Errors In a production React application using React.lazy for code splitting, dynamically imported modules are fetched as separate chunks. When a network failure or a missing asset occurs—such as a 404 error resulting from a deployment mismatch or an incorrect publicPath —the browser console typically reports an uncaught promis
Our Vite production build prints the chunk size warning for chunks over 500 kB, and we need to decide how to handle it. As I understand it, build.chunkSizeWarningLimit only controls when the warning prints; it does not fail the build or change the output. The unresolved decision: our main chunk sits slightly above the limit. We could raise the limit to silen
Optimizing Chunk Loading Strategies Webpack utilizes the import() syntax and SplitChunksPlugin to decompose application code into on-demand chunks. While magic comments allow for webpackPrefetch and webpackPreload , the runtime behavior varies based on the dependency graph's complexity. The primary goal is to balance the initial page load time against the la
Goal Minimize the amount of data transferred for a single page that receives a small number of visits per month. Constraints & Uncertainty Rollup removes unused ES module exports by default, but the extent of size reduction depends on side‑effect annotations and the presence of dynamic imports. Manual chunks can split the bundle into route‑specific piece
Our Rollup build uses format "es" with two entry points and dynamic imports, so Rollup automatically factors shared modules into shared chunks. We need repeatable, cache-friendly output: [hash] placeholders in chunkFileNames should only change when the code that chunk contains actually changes. The trade-off is between two documented approaches. Default chun
Goal is to configure a Rollup library build that maximizes downstream tree-shaking while keeping the declared public API intact. Static tree-shaking relies on ES module syntax and accurate sideEffects metadata, and code splitting is driven by dynamic import() with manualChunks shaping. Output format choice between es and cjs changes interop helpers and expor
clojurescript
webpack
rollup
react
vite