Unverified Commit cc172bf2 authored by vercel-fleet-prod[bot]'s avatar vercel-fleet-prod[bot] Committed by GitHub

docs: remove outdated Turbopack stability labels

Co-authored-by: 's avatarTobias Koppers <1365881+sokra@users.noreply.github.com>
parent 7d42c9dc
......@@ -14,12 +14,12 @@ Next.js automatically optimizes bundles by code splitting, tree-shaking, and oth
There are two tools for analyzing your application's bundles:
- [Next.js Bundle Analyzer for Turbopack (experimental)](#nextjs-bundle-analyzer-experimental)
- [Next.js Bundle Analyzer for Turbopack](#nextjs-bundle-analyzer)
- [`@next/bundle-analyzer` plugin for Webpack](#nextbundle-analyzer-for-webpack)
This guide will walk you through how to use each tool and how to [optimize large bundles](#optimizing-large-bundles).
## Next.js Bundle Analyzer (Experimental)
## Next.js Bundle Analyzer
> Available in v16.1 and later. You can share feedback in the [dedicated GitHub discussion](https://github.com/vercel/next.js/discussions/86731) and view the demo at [turbopack-bundle-analyzer-demo.vercel.sh](https://turbopack-bundle-analyzer-demo.vercel.sh/).
......
......@@ -179,7 +179,7 @@ We recommend using Turbopack for development and production. Submit a comment to
### Turbopack configuration location
The `experimental.turbopack` configuration is out of experimental.
The Turbopack configuration moved from `experimental.turbopack` to the top-level `turbopack` option.
```ts filename="next.config.ts"
import type { NextConfig } from 'next'
......
---
title: turbopackChunking
description: Configure how Turbopack splits your client-side JavaScript into chunks in production.
version: experimental
---
{/* The content of this doc is shared between the app and pages router. You can use the `<PagesOnly>Content</PagesOnly>` component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
......@@ -10,8 +9,7 @@ version: experimental
`experimental.turbopackChunking` lets you configure Turbopack's production JavaScript
chunker. These options allow you to change the assumptions the chunker makes about user
behavior, tweak the raw size thresholds it uses, and enable the experimental component
chunks feature.
behavior, tweak the raw size thresholds it uses, and enable component chunks.
</AppOnly>
......@@ -126,9 +124,9 @@ being made is costly, however, smaller chunks are more likely to be re-usable ac
## Component Chunks
Producing component chunks is an experimental feature that aims to give you the initial
page load benefits of merged chunks without sacrificing reusability. This feature lets
the runtime dynamically choose whether to load a merged chunk as a single file, or to
Component chunks provide the initial page load benefits of merged chunks without
sacrificing reusability. This feature lets the runtime dynamically choose whether to
load a merged chunk as a single file, or to
load only the component chunks it doesn't already have. Additionally, chunks that were
already loaded as part of a merged chunk will not be re-downloaded.
......
......@@ -53,9 +53,9 @@ If your build environment never preserves `.next/cache`, set `turbopackFileSyste
## Version History
| Version | Changes |
| --------- | -------------------------------------------------------------- |
| `v16.3.0` | FileSystem caching is enabled by default for builds |
| `v16.1.0` | FileSystem caching is enabled by default for development |
| `v16.0.0` | Beta release with separate flags for build and dev |
| `v15.5.0` | Persistent caching released as experimental on canary releases |
| Version | Changes |
| --------- | -------------------------------------------------------- |
| `v16.3.0` | FileSystem caching is enabled by default for builds |
| `v16.1.0` | FileSystem caching is enabled by default for development |
| `v16.0.0` | Separate flags added for build and dev |
| `v15.5.0` | Persistent caching introduced on canary releases |
......@@ -58,7 +58,7 @@ Each rule in the `ignoreIssue` array is an object with the following fields:
An issue is suppressed when it matches the `path` **and** all other specified fields in a rule. If only `path` is provided, any issue from a matching file is suppressed.
> **Good to know:** Issue titles and descriptions may change between Turbopack versions. The `path` field is generally stable, but is not guaranteed to remain consistent for all issue types. When possible, prefer using more specific `path` patterns over `title` or `description` matching.
> **Good to know:** Prefer more specific `path` patterns over `title` or `description` matching.
### `path`
......
......@@ -14,7 +14,7 @@ Currently there are three options
- `'auto'` (default): evict after a snapshot only once enough memory has been allocated since the last eviction to make it worthwhile. Leverages thresholds and memory pressure feedback from the operating system.
- `'full'`: evict all possible data from memory every time we save to disk.
> **Good to know:** This option only has an effect in `next dev` sessions when the [FileSystem Cache](/docs/app/api-reference/config/next-config-js/turbopackFileSystemCache) is enabled, since eviction relies on data already being persisted to disk. It is experimental and under active development.
> **Good to know:** This option only has an effect in `next dev` sessions when the [FileSystem Cache](/docs/app/api-reference/config/next-config-js/turbopackFileSystemCache) is enabled, since eviction relies on data already being persisted to disk.
```ts filename="next.config.ts" switcher
import type { NextConfig } from 'next'
......@@ -41,6 +41,6 @@ module.exports = nextConfig
## Version Changes
| Version | Changes |
| --------- | --------------------------------------------------- |
| `v16.3.0` | `turbopackMemoryEviction` released as experimental. |
| Version | Changes |
| --------- | ------------------------------------- |
| `v16.3.0` | `turbopackMemoryEviction` introduced. |
---
title: turbopackRustReactCompiler
description: Use the native Rust port of the React Compiler with Turbopack instead of the Babel transform.
version: experimental
---
The `experimental.turbopackRustReactCompiler` option enables the native Rust version of the [React Compiler](/docs/app/api-reference/config/next-config-js/reactCompiler), running it directly inside Turbopack as native code instead of through Node.js as it does with the standard Babel version. This typically results in a noticeable performance improvement.
This option is released as experimental to gather feedback before it becomes the default.
```ts filename="next.config.ts" switcher
import type { NextConfig } from 'next'
......@@ -47,6 +44,6 @@ See the [`reactCompiler` option documentation](/docs/app/api-reference/config/ne
## Version History
| Version | Changes |
| --------- | --------------------------------------------------------------------------------------------------- |
| `v16.3.0` | Introduced the experimental `turbopackRustReactCompiler` option for the native Rust React Compiler. |
| Version | Changes |
| --------- | -------------------------------------------------------------------------------------- |
| `v16.3.0` | Introduced the `turbopackRustReactCompiler` option for the native Rust React Compiler. |
......@@ -98,7 +98,7 @@ Turbopack in Next.js has **zero-configuration** for the common use cases. Below
| **@import syntax** | **Supported** | Combine multiple CSS files. |
| **PostCSS** | **Supported** | Automatically processes PostCSS config files (`postcss.config.js`, `.mjs`, `.cjs`, `.ts`, `.mts`, `.cts`) in a Node.js worker pool. Useful for Tailwind, Autoprefixer, etc. |
| **Sass / SCSS** | **Supported** (Next.js) | For Next.js, Sass is supported out of the box. Custom Sass functions (`sassOptions.functions`) are not supported because Turbopack's Rust-based architecture cannot directly execute JavaScript functions, unlike webpack's Node.js environment. Use webpack if you need this feature. In the future, Turbopack standalone usage will likely require a loader config. |
| **Less** | Planned via plugins | Not yet supported by default. Will likely require a loader config once custom loaders are stable. |
| **Less** | Planned via plugins | Not yet supported by default. Will likely require a loader config once custom loader support is available. |
| **Lightning CSS** | **In Use** | Handles CSS transformations. Some low-usage CSS Modules features (like `:local/:global` as standalone pseudo-classes) are not yet supported. [See below for more details.](#unsupported-and-unplanned-features) |
### Assets
......@@ -451,7 +451,7 @@ Turbopack can be configured via `next.config.js` (or `next.config.ts`) under the
- **[`ignoreIssue`](/docs/app/api-reference/config/next-config-js/turbopackIgnoreIssue)**
Suppress specific Turbopack errors and warnings from the CLI output and error overlay.
Additionally, the following experimental options are available under `experimental` in `next.config.js`:
Additionally, the following Turbopack options are available under `experimental` in `next.config.js`:
| Option | Description | Default (dev) | Default (build) |
| ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ----------------------------- |
......@@ -460,7 +460,7 @@ Additionally, the following experimental options are available under `experiment
| `turbopackMinify` | Enable minification. Accepts a boolean, or `{ server, client, edge }` to configure each environment separately. | `false` | `true` |
| `turbopackSourceMaps` | Enable source maps. | `true` | `productionBrowserSourceMaps` |
| `turbopackInputSourceMaps` | Enable extraction of source maps from input files. | `true` | `true` |
| `turbopackModuleFragments` | Currently in active development. This splits modules into fragments and chunks only import the used fragments of the modules. | `false` | `false` |
| `turbopackModuleFragments` | Split modules into fragments so chunks only import the used fragments of the modules. | `false` | `false` |
| `turbopackRemoveUnusedImports` | Enable removing unused imports. Requires `turbopackRemoveUnusedExports`. | `false` | `true` |
| `turbopackRemoveUnusedExports` | Enable removing unused exports. | `false` | `true` |
| `turbopackMangleExportNames` | Shorten the export names modules expose to each other, to reduce bundle size. A module whose export names can be observed (an escaping namespace object, a dynamic `import()`, a CommonJS `require()`) keeps its original names. | `false` | `false` |
......@@ -522,6 +522,6 @@ Turbopack is a **Rust-based**, **incremental** bundler designed to make local de
| Version | Changes |
| --------- | ------------------------------------------------------------------------------------------------------------------ |
| `v16.0.0` | Turbopack becomes the default bundler for Next.js. Automatic support for Babel when a configuration file is found. |
| `v15.5.0` | Turbopack support for `build` beta |
| `v15.3.0` | Experimental support for `build` |
| `v15.5.0` | Turbopack support for `build` expanded |
| `v15.3.0` | Turbopack support for `build` introduced |
| `v15.0.0` | Turbopack for `dev` stable |
---
title: turbopackChunking
description: Configure how Turbopack splits your client-side JavaScript into chunks in production.
version: experimental
source: app/api-reference/config/next-config-js/turbopackChunking
---
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment