Audit my JavaScript bundle for dependency bloat and shrink it. 1. Visualize: generate a bundle analysis (source-map-explorer, webpack-bundle-analyzer, or my build tool's equivalent) for the production build and list the largest contributors by parsed size. 2. Hunt the usual suspects: moment.js (replace with date-fns or Intl), full lodash imports (switch to per-method imports or native equivalents), entire icon libraries imported for a handful of icons, multiple versions of the same package bundled due to transitive dependencies, and heavy libraries loaded on pages that never use them. 3. Tree-shaking check: confirm my build is actually tree-shaking (ESM imports, sideEffects flags honored) and fix import styles that defeat it, like importing from a library's root when per-module imports shake better. 4. Remove the dead: find dependencies in package.json that nothing imports anymore and uninstall them. Check devDependencies did not leak into the client bundle. 5. Code-split: any large dependency used on only one route or behind a user action (charts, editors, PDF tools) moves to a dynamic import so it loads on demand, not in the initial bundle. 6. Verify: rebuild and report initial bundle size before and after, plus confirmation that the features using moved dependencies still work (lazy-loaded, with a loading state if the chunk takes time). Do not replace a library I actively use just to chase size if the replacement means rewriting working code; prioritize removals, dedupes, and code-splitting first. Do not break SSR if my app server-renders; dynamic imports need the right handling there. Give me: the top bundle contributors, each change made and its size impact, and the final before/after comparison.