nextjs - ✅(Solved) Fix next.js 15.5.9 works on OpenBSD/adJ 7.8 but next.js 16 does not [1 pull requests, 8 comments, 4 participants]

nextjs2026-01-30 17:06:09

ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

vercel/next.js#89305•Fetched 2026-04-08 02:03:00

View on GitHub

Comments

Participants

Timeline

Reactions

Author

Participants

Assignees

Timeline (top)

commented ×8labeled ×2mentioned ×2subscribed ×2

Error Message

Run pnpm dev and you will see the error: Error: turbo.createProject is not supported by the wasm bindings.

Root Cause

✓ Starting...
Skipping creating a lockfile at /home/vtamara/tmp/a1616/.next/dev/lock because we're using WASM bindings Error: turbo.createProject is not supported by the wasm bindings.
at ignore-listed frames
⚠ Trying to load next-swc for unsupported platforms openbsd/x64

Fix Action

Fixed

Fixed by PR: Add a better error message for when turbopack cannot be loaded (https://github.com/vercel/next.js/pull/89633)

PR fix notes

PR #89633: Add a better error message for when turbopack cannot be loaded

Repository: vercel/next.js
Author: lukesandberg
State: closed | merged: True
Link: https://github.com/vercel/next.js/pull/89633

Description (problem / solution / changelog)

Add a more direct error message when next is running on a platform that turbopack doesn't support

document supported turbopack platforms

Testing

To test i just set NEXT_TEST_WASM=1 and ran a build

Error: Turbopack is not supported on this platform (darwin/arm64) because native bindings are not available. Only WebAssembly (WASM) bindings were loaded, and Turbopack requires native bindings.

To use Next.js on this platform, use Webpack instead:
  next dev --webpack

For more information, see: https://nextjs.org/docs/app/api-reference/turbopack#supported-platforms
    at ignore-listed frames

so it should work. Messaging probably could be better (there is also a messge about not being able to set the lockfile) but this should be much better

Fixes #89305

Changed files

docs/01-app/03-api-reference/08-turbopack.mdx (modified, +18/-0)
packages/next/errors.json (modified, +6/-1)
packages/next/src/build/swc/index.ts (modified, +7/-4)
packages/next/src/build/turbopack-analyze/index.ts (modified, +9/-0)
packages/next/src/build/turbopack-build/impl.ts (modified, +11/-0)
packages/next/src/server/dev/hot-reloader-turbopack.ts (modified, +12/-0)

Code Example

% npx --no-install next info
⚠ Trying to load next-swc for unsupported platforms openbsd/x64

Operating System:
  Platform: openbsd
  Arch: x64
  Version: APRENDIENDODEJESUS.MP#0
  Available memory (MB): 15102
  Available CPU cores: 8
Binaries:
  Node: 22.20.0
  npm: 11.7.0
  Yarn: 1.22.22
  pnpm: 10.28.0
Relevant Packages:
  next: 16.1.6 // Latest available version is detected (16.1.6).
  eslint-config-next: N/A
  react: 19.2.3
  react-dom: 19.2.3
  typescript: 5.9.3
Next.js Config:
  output: N/A

RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/vtamara/a1616

To Reproduce

On OpenBSD or adJ 7.8 create a next.js application

% npx create-next-app                                                       
Need to install the following packages:
[email protected]                                                                                                                                          
Ok to proceed? (y) y                                                                                                                                            
✔ What is your project named? … a1616                                                                                                                           
✔ Would you like to use the recommended Next.js defaults? › Yes, use recommended defaults
Creating a new Next.js app in /home/vtamara/tmp/a1616.

Using npm.                              

Initializing project with template: app-tw

Configure tailwindcxx with WASM by adding to package.json:

 "pnpm": {
    "overrides": {
      "lightningcss": "npm:lightningcss-wasm",
      "@tailwindcss/oxide": "npm:@tailwindcss/oxide-wasm32-wasi"
    }
  }

Run pnpm install

Run pnpm dev and you will see the error:

 > [email protected] dev /home/vtamara/tmp/a1616                                       
 > next dev                                                                                                                                                      
                                                                                                                                                                 
 ⚠ Port 3000 is in use by an unknown process, using available port 3001 instead.                                                                                 
 ⚠ Trying to load next-swc for unsupported platforms openbsd/x64                                                                                                 
   Using cached swc package @next/swc-wasm-nodejs...                                                                                                             
 ▲ Next.js 16.1.6 (Turbopack)                                                                                                                                    
 - Local:         http://localhost:3001                                                                                                                          
 - Network:       http://192.168.4.44:3001                                                                                                                       
                                                                                                                                                                 
 ✓ Starting...                                                                                                                                                   
   Skipping creating a lockfile at /home/vtamara/tmp/a1616/.next/dev/lock because         we're using WASM bindings
 Error: `turbo.createProject` is not supported by the wasm bindings.             
     at ignore-listed frames                                                     
 ⚠ Trying to load next-swc for unsupported platforms openbsd/x64                                                                                                 
                                                                                 
  ELIFECYCLE  Command failed with exit code 1.

Current vs. Expected behavior

That nextjs 16 could be used in development and production mode without Turbopack so it would work like with next.js 15.3.9 or that Turbopack would work with wasm:

Create a next.js 15.3.9 application without Turbopack:

   % npx [email protected]                                               
   Need to install the following packages:                                        
   [email protected]                                                         
   Ok to proceed? (y) y                                                           
   ✔ What is your project named? … a1539                                          
   ✔ Would you like to use TypeScript? … No / Yes                                 
   ✔ Would you like to use ESLint? … No / Yes                                     
   ✔ Would you like to use Tailwind CSS? … No / Yes                               
   ✔ Would you like your code inside a `src/` directory? … No / Yes               
   ✔ Would you like to use App Router? (recommended) … No / Yes
   ✔ Would you like to use Turbopack for `next dev`? … No / Yes
   ✔ Would you like to customize the import alias (`@/*` by default)? … No / Yes

Configure lightningcss (used by tailwindcss) to use wasm by adding to package.json:

 "pnpm": {
     "overrides": {
       "lightningcss": "npm:lightningcss-wasm",
       "@tailwindcss/oxide": "npm:@tailwindcss/oxide-wasm32-wasi"
     }
 }

Run pnpm dev and see the example with a browser at locahost:3000

Provide environment information

% npx --no-install next info
⚠ Trying to load next-swc for unsupported platforms openbsd/x64

Operating System:
  Platform: openbsd
  Arch: x64
  Version: APRENDIENDODEJESUS.MP#0
  Available memory (MB): 15102
  Available CPU cores: 8
Binaries:
  Node: 22.20.0
  npm: 11.7.0
  Yarn: 1.22.22
  pnpm: 10.28.0
Relevant Packages:
  next: 16.1.6 // Latest available version is detected (16.1.6).
  eslint-config-next: N/A
  react: 19.2.3
  react-dom: 19.2.3
  typescript: 5.9.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

create-next-app

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

I tested with 16.0.0 and noticed that this problem starts to happen with that version and it doesn't give option to disable turbopack neither has WASM support in turbopack.

extent analysis

TL;DR

The most likely fix is to downgrade to Next.js 15.3.9, which does not use Turbopack and supports WASM bindings.

Guidance

The error message indicates that turbo.createProject is not supported by the WASM bindings, suggesting a compatibility issue with Turbopack and WASM.
Downgrade to Next.js 15.3.9, which does not use Turbopack and supports WASM bindings, as demonstrated in the "Current vs. Expected behavior" section.
Verify that the issue is resolved by running pnpm dev after downgrading to Next.js 15.3.9.
If downgrading is not feasible, consider waiting for a future release of Next.js that supports Turbopack with WASM bindings.

Example

No code snippet is provided as the issue is related to compatibility and versioning.

Notes

The issue is specific to OpenBSD and Next.js 16.1.6, and the provided environment information suggests that the problem starts with version 16.0.0. Downgrading to Next.js 15.3.9 is a temporary workaround until a future release addresses the compatibility issue.

Recommendation

Apply the workaround by downgrading to Next.js 15.3.9, as it is a known working version that supports WASM bindings without Turbopack.

Vote matrix · Quick signals

Works

Did the solution work? Tap to confirm.

Easy Fix

Was it a quick fix?

Time Saver

Did it save you time?

Blocking

Was it severely blocking?

Common Issue

Are others likely hitting this too?

Flaky / Intermittent

Is it intermittent?

Verified / Reproducible

Can you reproduce it reliably?

#database connection #vector store #embedding generation #cache error #pipeline error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Data

Security

Network

Code

UI/UX

Text

System

Multimedia

Protocol

API

Engineering

nextjs - ✅(Solved) Fix next.js 15.5.9 works on OpenBSD/adJ 7.8 but next.js 16 does not [1 pull requests, 8 comments, 4 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fixed

PR fix notes

PR #89633: Add a better error message for when turbopack cannot be loaded

Description (problem / solution / changelog)

Testing

Changed files

Code Example

Link to the code that reproduces this issue

To Reproduce

Current vs. Expected behavior

Provide environment information

Which area(s) are affected? (Select all that apply)

Which stage(s) are affected? (Select all that apply)

Additional context

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

Still need to ship something?

TRENDING

nextjs - ✅(Solved) Fix next.js 15.5.9 works on OpenBSD/adJ 7.8 but next.js 16 does not [1 pull requests, 8 comments, 4 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fixed

PR fix notes

PR #89633: Add a better error message for when turbopack cannot be loaded

Description (problem / solution / changelog)

Testing

Changed files

Code Example

Link to the code that reproduces this issue

To Reproduce

Current vs. Expected behavior

Provide environment information

Which area(s) are affected? (Select all that apply)

Which stage(s) are affected? (Select all that apply)

Additional context

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

Still need to ship something?

RELATED_DISCOVERY

TRENDING