Skip to content

[turbopack] Flag turbopackInferModuleSideEffects so it is only enabled in canary builds #87215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lukesandberg merged 1 commit into from
Dec 16, 2025
+2 −1
Merged

[turbopack] Flag turbopackInferModuleSideEffects so it is only enabled in canary builds #87215

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion packages/next/src/server/config-shared.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -469,7 +469,7 @@ export interface ExperimentalConfig {
* analyze module code to determine if it has side effects. This can improve tree shaking
* and bundle size at the cost of some additional analysis.
*
* Defaults to `true`.
* Defaults to `true` in canary builds only
*/
turbopackInferModuleSideEffects?: boolean

Expand Down Expand Up @@ -1576,6 +1576,7 @@ export const defaultConfig = Object.freeze({
mcpServer: true,
turbopackFileSystemCacheForDev: true,
turbopackFileSystemCacheForBuild: false,
turbopackInferModuleSideEffects: !isStableBuild(),
},
htmlLimitedBots: undefined,
bundlePagesRouterDependencies: false,
Expand Down
Loading