bundle-size-analyzer

Tree-shaking reduces bundle size by eliminating unused module code during the build. The analyzer verifies tree-shaking by checking if your imports use named exports, ensuring proper dead code elimination.

Yes, you can analyze bundle size for web apps and libraries using npm or Yarn projects. The tool scans your project root to audit dependencies and validate tree-shaking across development, build, and CI workflows.

Modern replacements for heavy JavaScript libraries include date-fns for moment.js and lodash-es for lodash. The analyzer suggests these 1:1 replacements and shows how named imports enable proper tree-shaking.

Fix tree-shaking not working by ensuring your imports use named exports like `debounce` from lodash-es instead of default imports. The analyzer checks named imports in your package.json to validate proper tree-shaking.