ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Rollup tree-shaking removes dead code, but unused exports often persist. This guide diagnoses the conditions, provides a cause table, ordered checks, and fixes to reclaim bundle size.
Deno executes TypeScript files natively without a separate compile step. This guide covers running .ts files directly, adding permissions, enabling static checks with --check, importing remote modules, and handling startup latency and cache issues.
Configure Rollup tree-shaking to remove unused ES module exports from browser bundles, with a worked example and verification steps.
Decide between Vite's esnext ESM target and legacy fallback bundles. Compare build size, speed, and browser support with a practical configuration and validation checklist.
Learn how Rollup's preserveModules option keeps your ES module file structure intact while allowing tree‑shaking of external dependencies.
Learn how Vite’s native ES module serving eliminates bundling in development, giving near‑instant start and precise Hot Module Replacement, with a concrete setup example and notes on browser support and monorepo considerations.
Rollup's tree shaking uses ES Module static structure to drop unused exports. Learn how the treeshake config tunes aggressiveness, why sideEffects flags matter, and how to verify the output in CI.
How Rollup decides which modules to drop, why package.json sideEffects is a trust boundary, and the checks that catch a wrong declaration before users do.
Vite's speed comes from two decisions: serving source as native ES modules and pre-bundling dependencies once. Here's how both work, how to verify them, and where they break down.
rollup
vite
vitejs