ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #rollup
Learn how Notion Relations and Rollups automate cross‑table aggregates like task counts and completion percentages for lightweight project tracking.
Rollup's manualChunks lets you split stable vendor dependencies from churning app code so browsers keep cached third-party code across deploys. Here's a working config, how to verify it, and when splitting backfires.
Reduce initial bundle size by using Rollup's dynamic import() and manualChunks to isolate vendor libraries and lazy-load feature modules on demand.
Learn how Rollup's tree shaking removes unused code through static analysis of ES Modules and how to avoid common pitfalls like side effects and CommonJS dependencies.
Learn how to configure Rollup’s built‑in tree‑shaking to drop dead exports, understand its limits, and verify that the bundle really shrinks.
Rollup wraps every bundled module, including the ES module entry point, in a function where this is undefined under strict mode. An entry point that references top-level this while expecting the global object then produces the documented THIS_IS_UNDEFINED warning, and the runtime binding stays undefined even when the warning is filtered out. The context and
Automatic Chunking Behavior Rollup automatically creates separate chunks for modules imported via dynamic import() . However, the internal algorithm used to determine which modules share a chunk remains opaque, and the tool does not enforce a default maximum chunk size. Constraints and Uncertainty While output.manualChunks allows for explicit grouping, it re
Rollup sequencers often provide retryable transaction endpoints to handle state-changing operations during network instability. While many implementations support idempotency keys to deduplicate these writes, the current protocol specification does not mandate their use as a requirement. Without a protocol-level constraint, clients may currently rely on stat
A low-traffic site wants its JavaScript payload kept as small as possible so per-visit transfer and deployment overhead stay low. Rollup's tree-shaking is the main lever for cutting unused code from the bundle, and the plan is to rely on its static analysis of ES modules rather than manually pruning imports across the dependency graph. The unresolved point i
javascript