Repository navigation
Clarification on turbopackFileSystemCacheForDev Being Marked Experimental in Next.js 16.1 #87357
|
Next.js The Next.js 16.1 Blog also states:
What’s the reason this setting continues to appear under the experimental section? |
Replies: 2 comments
|
The apparent contradiction makes sense once you understand what the blog post and the config option are describing separately. "Stable and on by default" means the feature is enabled automatically when you run The Think of the In practice:
The docs could do a better job of distinguishing between "this option is experimental" and "this option controls a stable feature but lives in the Turbopack config namespace." |
|
The only reason is that you have the option to opt-out, but that flag itself may not necessarily exist in later majors, or there might different ways to control the feature. The feature itself, fileSystemCacheForDev is OK and stable. |
The only reason is that you have the option to opt-out, but that flag itself may not necessarily exist in later majors, or there might different ways to control the feature. The feature itself, fileSystemCacheForDev is OK and stable.