Link to the code that reproduces this issue

https://github.com/vtamara/a1616

To Reproduce

1. On OpenBSD or adJ 7.8 create a next.js application

   % npx create-next-app                                                       
   Need to install the following packages:
   create-next-app@16.1.6                                                                                                                                          
   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 
   

2. Configure tailwindcxx with WASM by adding to package.json:

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

3. Run pnpm install

4. Run pnpm dev and you will see the error:

    > a1616@0.1.0 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:

1. Create a next.js 15.3.9 application without Turbopack:

      % npx create-next-app@15.3.9                                               
      Need to install the following packages:                                        
      create-next-app@15.3.9                                                         
      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
   

2. 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"
        }
    }
   

3. 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.