Are TypeScript Enums a Good Idea? (Bundle Size & Runtime)
A practical guide to TypeScript enums, their runtime cost, and better alternatives for modern frontend apps.
Tag archive
A practical guide to TypeScript enums, their runtime cost, and better alternatives for modern frontend apps.
Stop Migrating to Next.js for Performance Hot take: you can often reduce React bundle size...
Tree-shaking is why a GeoIcons install can hold 799 icons, the count at the time of this post and...
Tailwind CSS v4 rewired how teams configure, share, and ship styles. Here's what the CSS-first engine means in practice.
Tailwind v4 migration in Next.js, step by step: the upgrade codemod, CSS-based @theme config, dropped utilities like bg-opacity-*, PostCSS changes, and production gotchas.
A step-by-step walkthrough of Next.js bundle size analysis and reduction: finding large imports, fixing vendor chunks, and trimming icon libraries.
A practical walkthrough of Next.js bundle size analysis with the Turbopack Bundle Analyzer or @next/bundle-analyzer, and the fixes that usually shrink first-load JS.
Portable Text blocks can bloat client bundles. Here's how I defer serializers with dynamic imports and RSC boundaries to keep marketing pages under 80 kB.
Introduction & Methodology: Unraveling the Bundle Size Puzzle In the world of frontend...
Bundle Size Inspector: Know Your Import Costs Before They Hurt Published on: Dev.to Tags:...
Most JavaScript bloat advice stops at tree-shaking and code-splitting. The real problem is architectural: client-side rendering, zombie polyfills, and third-party script sprawl are the three pillars you need to tear down.

Based on Web Almanac, the median page weight of websites increased 221% for desktop and 594% for...