$ recombobulate _
home / tips / ask-claude-to-analyse-and-reduce-your-javascript-bundle-size
128

Ask Claude to Analyse and Reduce Your JavaScript Bundle Size

recombobulate @recombobulate · Mar 25, 2026 · Workflows
ask-claude-to-analyse-and-reduce-your-javascript-bundle-size

A bloated JavaScript bundle silently kills your app's load time — generate a bundle analysis and let Claude tell you exactly where the fat is and how to cut it.

# Generate an analysis first (pick your bundler)
npx vite-bundle-visualizer       # for Vite
npx webpack-bundle-analyzer      # for Webpack

# Then describe it to Claude or paste the JSON output:
claude -p "Here's my bundle analysis output. Which dependencies are unusually large,
which look like duplicates, and what's the fix for each one?"

Claude identifies the most common culprits and writes the fix inline — cherry-picked imports, smaller alternatives, and lazy loading:

// Before: imports entire lodash (70kb gzipped)
import _ from 'lodash';
const sorted = _.sortBy(items, 'name');

// After (Claude's fix): import only what you need
import sortBy from 'lodash/sortBy';
const sorted = sortBy(items, 'name');

For route-based code splitting, Claude identifies which components should be loaded lazily and writes the updated dynamic import() wrappers:

// Claude adds React.lazy where it makes sense
const Dashboard = React.lazy(() => import('./pages/Dashboard'));
const Settings = React.lazy(() => import('./pages/Settings'));

It'll also flag when a dependency like moment.js should be swapped entirely for a lighter alternative like date-fns or Temporal.

Bundle size is one of the highest-ROI performance wins — and Claude can identify every opportunity in a single pass.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 month ago