fix(turbopack): prevent TypeScript from being bundled in standalone output #87262
+65
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Exclude dev-only dependencies from being traced into the .next/standalone output when using Turbopack, preventing large build-time tools (e.g. TypeScript) from being bundled into the runtime artifact.
Why?
When output: "standalone" is enabled with Turbopack, devDependencies are currently traced and copied into the standalone bundle, even though they are never required at runtime.
This leads to significantly larger standalone outputs (e.g. typescript ~20 MB) and unexpected Docker image bloat.
Webpack does not exhibit this behavior, so this is a Turbopack-specific issue.
How?
Treat packages declared as devDependencies as untraced externals during standalone output generation.
Update the server resolver logic to respect this distinction while keeping existing external resolution behavior unchanged.
This ensures only runtime-required dependencies are included in .next/standalone.
Fixes and closes #86981