Turbopack
nextjs.org
What it is
Turbopack is an incremental JavaScript and TypeScript bundler written in Rust and built into Next.js. It supports the Pages Router and App Router for local development and is the default bundler in Next.js for basic use without configuration. It parallelizes work across CPU cores, caches results at the function level and persists them between runs. Lazy bundling processes only what the development server requests, which can reduce initial compile time and memory use. Its support includes JavaScript, TypeScript, ECMAScript, CommonJS, ESM and Babel configuration detection in Next.js 16, along with JSX, Fast Refresh and React Server Components for the App Router. CSS support includes global CSS, CSS Modules, nesting, PostCSS and Sass/SCSS, but not custom Sass functions. It also handles static image and font imports, JSON, aliases and custom extensions. Native bindings are available for Linux, macOS and Windows. Turbopack is included in Next.js with no separate price stated. It does not perform TypeScript type checking, and it does not support webpack plugins.
Spec sheet
- Purpose
- Turbopack is an incremental JavaScript and TypeScript bundler written in Rust and built into Next.js.Read 7 Oct 2026 · nextjs.org
- Asset and resolution support
- It supports static image and font imports, JSON imports, TypeScript path aliases, manual aliases, and custom extensions.Read 7 Oct 2026 · nextjs.org
- CSS and styling
- It supports global CSS, CSS Modules, CSS nesting, PostCSS, and Sass/SCSS in Next.js; custom Sass functions are unsupported.Read 7 Oct 2026 · nextjs.org
- Default bundler
- Turbopack is the default bundler in Next.js, with no configuration required for basic use.Read 7 Oct 2026 · nextjs.org
- Framework features
- It supports JSX, Fast Refresh, and React Server Components for the Next.js App Router.Read 7 Oct 2026 · nextjs.org
- Incremental builds
- It parallelizes work across CPU cores, caches results at the function level, and persists results to disk between runs.Read 7 Oct 2026 · nextjs.org
- Integration limit
- Turbopack does not support webpack plugins, although it supports webpack loaders.Read 7 Oct 2026 · nextjs.org
- Language support
- It supports JavaScript, TypeScript, ECMAScript, CommonJS, ESM, and Babel configuration detection in Next.js 16.Read 7 Oct 2026 · nextjs.org
- Lazy bundling
- It bundles only what the development server requests, which can reduce initial compile time and memory use.Read 7 Oct 2026 · nextjs.org
- Other limitations
- Yarn Plug'n'Play and experimental URL imports are not planned for Turbopack support in Next.js.Read 7 Oct 2026 · nextjs.org
- Support channel
- The documentation says users can attach a generated Turbopack trace file when filing a GitHub issue to help the Next.js team investigate performance or memory issues.Read 7 Oct 2026 · nextjs.org
- Supported systems
- Native bindings are available for macOS, Windows, and Linux on x64 and ARM64; Linux supports glibc and musl.Read 7 Oct 2026 · nextjs.org
- Type checking
- Turbopack does not perform TypeScript type checking; the documentation recommends running tsc --watch or using an IDE for checks.Read 7 Oct 2026 · nextjs.org
- Use
- It supports both the Pages Router and App Router for local development.Read 7 Oct 2026 · nextjs.org
Plans and prices
Strong points and limits
Strong points
- Included in Next.js at no separate stated price.
- Supports both Next.js routers for local development.
- Persists cached results between runs.
- Supports Fast Refresh and React Server Components.
- Native bindings for Linux, macOS and Windows.
Limits
- Does not perform TypeScript type checking.
- Does not support webpack plugins.
- Custom Sass functions are unsupported.
- Yarn Plug'n'Play support is not planned.
Who it suits
Turbopack suits Next.js developers seeking a local-development bundler with incremental builds and framework features such as Fast Refresh. Developers who need TypeScript checking or webpack plugins should account for those limitations.
Verdict
Turbopack combines incremental bundling with Next.js framework and asset support, and basic use requires no configuration. Its lack of type checking and webpack plugin support are important limits to weigh.
Where Specifiction places it
- JavaScript Build Tools#18 of 277.4