Skip to content

Conversation

@Aakash0440
Copy link

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

@nextjs-bot nextjs-bot added create-next-app Related to our CLI tool for quickly starting a new Next.js application. Documentation Related to Next.js' official documentation. type: next labels Feb 2, 2026
@nextjs-bot
Copy link
Collaborator

Allow CI Workflow Run

  • approve CI run for commit: 8ba5274

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

1 similar comment
@nextjs-bot
Copy link
Collaborator

Allow CI Workflow Run

  • approve CI run for commit: 8ba5274

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

const shouldUseTurbopack =
!!opts.turbo && turboEnabledInConfig && !runningWithWasmBindings

if (!!opts.turbo && !shouldUseTurbopack) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if (!!opts.turbo && !shouldUseTurbopack) {
if (!!opts.turbo && runningWithWasmBindings) {

Misleading WASM warning shown when Turbopack is disabled via config, not due to WASM bindings

Fix on Vercel

@mischnic
Copy link
Member

mischnic commented Feb 2, 2026

It sounds like you are just looking for the --webpack flag?

@bgw
Copy link
Member

bgw commented Feb 2, 2026

There's already a --webpack flag. Did you try that? Did that not work for you?

We don't want an automatic fallback mechanism because it's a pretty significant choice to fall back to webpack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

create-next-app Related to our CLI tool for quickly starting a new Next.js application. Documentation Related to Next.js' official documentation. type: next

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants