feat(turbopack): add opt-out for WASM platforms #89386
Open
+161
−2
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.
Next.js 16 fails on OpenBSD due to mandatory Turbopack WASM bindings, which are not supported on all platforms.
This PR adds the ability to opt-out of Turbopack and provides an automatic fallback to webpack on unsupported platforms, including OpenBSD.
Changes:
Added --no-turbo CLI flag
Added experimental.turbo.enabled config option
Automatic detection of WASM platforms (fallback to webpack)
Updated create-next-app to skip Turbopack prompt on unsupported platforms
Added integration tests for fallback behavior
Updated documentation (README.md, 11-turbopack.mdx, turbopack-unsupported-platform.mdx)
Testing:
Tested on OpenBSD 7.8 (fallback works)
Tested on Linux (Turbopack still works by default)
Integration tests added
Manual CLI and next.config.js flag verification