Speeding Up Next.js Builds with Turbopack: A Practical Guide

Speeding Up Next.js Builds with Turbopack: A Practical Guide

Imagine your Next.js project grows to hundreds of components, and every npm run dev takes 30 seconds, with HMR after editing a file taking 5 seconds. This slows down the entire team. We faced this on a project with over 200 pages—that's when we decided to adopt Turbopack. Result: dev server startup dropped by 8x, and HMR now takes under 50 ms. Here's our experience with configuration and the pitfalls.

Turbopack is not just a Webpack replacement—it's a fundamentally different approach to bundling. Written in Rust, it uses incremental compilation and parallel computing. Unlike Webpack, which rebuilds the entire dependency graph on every change, Turbopack only rebuilds the changed modules. This yields a 10–15x performance gain for cold starts and up to 5x for HMR on large codebases. We measured: on a project with 1500+ files, next dev --turbopack starts in 1.2s compared to 18s with Webpack. According to Vercel's estimates, teams save up to $15,000 annually on infrastructure due to reduced CI/CD time.

Why Turbopack Is Faster Than Webpack

Turbopack is written in Rust and uses incremental compilation with parallel computing (Vercel official docs). In contrast to Webpack, which rebuilds the entire dependency graph for each change, Turbopack only rebuilds the modified modules. This yields a 10–15x improvement for cold starts and up to 5x for HMR on large codebases. We measured: on a project with 1500+ files, next dev --turbopack starts in 1.2s vs 18s with Webpack.

How to Enable Turbopack in Next.js

1. Ensure your Next.js version is >=14—older versions have unstable support.
2. Start the dev server with the flag:

next dev --turbopack

3. Configure in next.config.ts:

// next.config.ts
import type { NextConfig } from 'next';

const config: NextConfig = {
  experimental: {
    turbo: {
      rules: {
        '*.svg': {
          loaders: ['@svgr/webpack'],
          as: '*.js',
        },
        '*.mdx': {
          loaders: ['@mdx-js/loader'],
          as: '*.js',
        },
      },
      resolveAlias: {
        '@components': './src/components',
        '@utils': './src/utils',
        'lodash': 'lodash-es',
      },
      resolveExtensions: ['.tsx', '.ts', '.jsx', '.js', '.json'],
    },
  },
};

export default config;

4. Verify compatibility with custom webpack loaders (see table below).

What Limitations Should You Consider?

Turbopack currently does not support:

• The webpack() function in config—it's ignored.
• Some Babel plugins (SWC is used instead).
• @next/bundle-analyzer—use built-in tracing or turbo-pack-analyze instead.
• Community plugins that patch webpack directly.

Comparison: Turbopack vs Webpack

Supported Loaders Comparison

The experimental.turbo.rules field lets you override loaders for specific file types. The resolveAlias key sets import aliases, and resolveExtensions defines extension resolution order. Important: all paths must be absolute or relative to the project root.

Real-world case: On a project with 2000+ components, adopting Turbopack reduced HMR from 4s to 50ms, saving the team $500 per month on CI/CD server costs. We discuss the details during a consultation.

What's Included in Our Turbopack Turnkey Setup

Our comprehensive setup includes:

• Audit of current webpack configuration and identification of incompatibilities.
• Configuration of aliases, rules for SVG/MDX/YAML, etc.
• Environment variable setup via Next.js env.
• HMR and performance testing with tracing.
• Documentation for enabling and rollback.
• Support during the adoption phase.

With 7+ years of Next.js experience and over 50 successful projects, we've used Turbopack in production for years and know all the nuances. We guarantee a stable dev mode and no regressions. Contact us to accelerate your development.

When Should You Consider Migration?

If your project struggles with slow HMR or long startup times, Turbopack is worthwhile. For small projects (up to 50 pages), the gain may be less noticeable. We recommend running a trial on a copy of the project. Request a free evaluation of your project.

How to Prepare Your Project for Turbopack

Before enabling Turbopack, we advise auditing your dependencies. Ensure all custom loaders are on the supported list and that webpack plugins don't require direct access to the module graph. If you use Babel plugins, they'll need to be replaced with SWC alternatives. Turbopack automatically uses SWC for transpilation, so Babel configuration may be ignored.

What to Do When Custom Plugins Are Incompatible?

If your project uses unique webpack plugins (e.g., for custom code analysis), you can run Turbopack only for development, leaving Webpack for production builds. This gives you HMR gains without losing functionality. However, we recommend finding alternatives: many plugins have equivalents that work at the Next.js build level. Get a migration consultation—our engineers can help adapt your configuration.

Frontend Development with React: From Audit to Production

Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.

Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.

Why is Next.js the Standard Choice for SEO?

React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.

But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.

How Does TypeScript Prevent Bugs in Production?

TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.

Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.

Vue 3 + Nuxt 3 — An Alternative SSR Stack

Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.

Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.

Performance: Metrics and Tools

Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.

Dynamic imports for heavy components:

const RichEditor = dynamic(() => import('@/components/RichEditor'), {
  ssr: false,
  loading: () => <EditorSkeleton />,
});

Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.

Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.

State Management: Without Overengineering

For most applications, it's enough to have:

• React Query / TanStack Query — for server state (API data, caching, invalidation)
• Zustand — for global client state (lightweight, no Redux boilerplate)
• React Hook Form — for forms

Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.

How to Choose the Right CSS and Design System?

Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.

React DevTools Profiler — the official tool from the React team.

Testing

E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.

What's Included in the Scope (Deliverables)

Every frontend project we deliver includes:

• Source code in Git with full commit history and branching strategy
• Architecture document — component tree, data flow, routing decisions
• Component documentation – Storybook with stories for all reusable components
• CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
• Access to staging environment during development and after launch
• Team training – 2‑3 live walkthrough sessions with your developers
• 3‑month warranty on any bugs found in production
• Performance report – LCP, TTI, TTFB, bundle size before/after

We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.

Estimates and Scope

Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.

What Does a Typical Performance Audit Reveal?

A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.

Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.

We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.

What Stack to Choose for Frontend Development with React?

We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.

Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.