Enable rootParams by default#93863
Conversation
|
Notifying the following users due to files changed in this PR based on this repo's notify modifiers: @timneutkens, @ijjk, @shuding, @huozhi: |
5a5f214 to
2609941
Compare
rootParams is now available by default. the flag is removed. There are still intentional limitations. For instance rootParams cannot be used in route handlers and Server Actions. The feature will be expanded with some support for this in the future.
2609941 to
e83b672
Compare
Stats from current PR🔴 1 regression
📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles
Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📎 Tarball URLCommit: e83b672 |
Failing test suitesCommit: e83b672 | About building and testing Next.js
Expand output● Error overlay - RSC build errors › next/root-params › importing a non-existent getter from 'next/root-params'
Expand output● typescript-app-type-declarations › should write a new next-env.d.ts if none exist
Expand output● typescript-app-type-declarations › should write a new next-env.d.ts if none exist |
rootParams is now available by default. the flag is removed.
There are still intentional limitations. For instance rootParams cannot be used in route handlers and Server Actions. The feature will be expanded with some support for this in the future.