"next dev --turbo" fails in WASM with error (`turbo.createProject` is not supported by the wasm bindings) #75665

theshadowagent · 2024-09-26T15:36:01Z

theshadowagent
Sep 26, 2024

Link to the code that reproduces this issue

https://stackblitz.com/edit/stackblitz-starters-yew3c9

To Reproduce

Start next dev server with Turbopack (next dev --turbo) in WASM (e.g. using webcontainers.io)
The dev command fails with error

~/projects/stackblitz-starters-yew3c9
❯ npm install

added 10 packages, and changed 6 packages in 34s

144 packages are looking for funding
  run `npm fund` for details

~/projects/stackblitz-starters-yew3c9 34s
❯ npx next dev --turbo
  ▲ Next.js 15.0.0-canary.171 (turbo)
  - Local:        http://localhost:3000

 ✓ Starting...
   Downloading swc package @next/swc-wasm-nodejs... to /home/.cache/next-swc
Error: `turbo.createProject` is not supported by the wasm bindings.
    at Object.createProject (/home/projects/stackblitz-starters-yew3c9/node_modules/next/dist/build/swc/index.js:808:31)
    at createHotReloaderTurbopack (/home/projects/stackblitz-starters-yew3c9/node_modules/next/dist/server/dev/hot-reloader-turbopack.js:121:42)
    at async startWatcher (/home/projects/stackblitz-starters-yew3c9/node_modules/next/dist/server/lib/router-utils/setup-dev-bundler.js:164:38)
    at async setupDevBundler (/home/projects/stackblitz-starters-yew3c9/node_modules/next/dist/server/lib/router-utils/setup-dev-bundler.js:814:20)
    at async Span.traceAsyncFn (/home/projects/stackblitz-starters-yew3c9/node_modules/next/dist/trace/trace.js:157:20)
    at async initialize (/home/projects/stackblitz-starters-yew3c9/node_modules/next/dist/server/lib/router-server.js:87:30)
    at async Server.eval (/home/projects/stackblitz-starters-yew3c9/node_modules/next/dist/server/lib/start-server.js:266:36)

Current vs. Expected behavior

I expected next dev --turbo to work in WASM mode so I could have fast hot reloading, but it throws this error

Provide environment information

❯ npx next info

Operating System:
  Platform: linux
  Arch: x64
  Version: Ubuntu 20.04.0 LTS
  Available memory (MB): NaN
  Available CPU cores: 8
Binaries:
  Node: 18.20.3
  npm: 10.2.3
  Yarn: 1.22.19
  pnpm: 8.15.6
Relevant Packages:
  next: 15.0.0-canary.171 // Latest available version is detected (15.0.0-canary.171).
  eslint-config-next: 13.5.1
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A

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

Turbopack

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

next dev (local)

Additional context

I tested my reproduction against "15.0.0-canary.171" (latest canary release), and "14.2.13" (latest stable release). On stable it outputs a different error: TypeError: bindings.turbo.createProject is not a function.

I found the code that throws this:

next.js/packages/next/src/build/swc/index.ts

Line 1063 in 3ed9f4b

createProject: function (

Is wasm bindings support planned for turbopack anytime soon? Was very bummed to see this, since it considerably slows down next.js in browser IDEs.

samcx · 2024-10-01T06:29:05Z

samcx
Oct 1, 2024
Maintainer

@theshadowagent Thank you for submitting an issue!

I was not able to :repro: this.

0 replies

abhi12299 · 2024-10-01T14:34:39Z

abhi12299
Oct 1, 2024

the link provided works fine - no WASM errors on stackblitz

0 replies

theshadowagent · 2024-10-02T10:09:41Z

theshadowagent
Oct 2, 2024
Author

@samcx @abhi12299
Here's an update on how to reproduce:

Open the Stackblitz link I provided & stop the existing terminal command using Ctrl+C. The issue is that Stackblitz runs next dev without --turbo flag by default (specifically, it runs npm install && npx next dev)
Manually run npm install && npm run dev which runs the next dev --turbo command and fails

Apologies for confusing you here – I couldn't find a way to change the default run command in Stackblitz

Thanks for the swift response!

0 replies

theshadowagent · 2024-10-02T10:16:23Z

theshadowagent
Oct 2, 2024
Author

Also wanted to add about why it's important for me:
My default next14 + shadcn + tailwind project takes ~60 seconds to boot in Webcontainers without --turbo flag, and 83% of the time is spent on the compile step, which I suspect takes so long due to using Webpack instead of Turbopack.

0 replies

timneutkens · 2024-10-04T09:51:35Z

timneutkens
Oct 4, 2024
Maintainer

Turbopack does not have a WebAssembly build currently so I'm not expecting it to work on Stackblitz right now.

It's not unexpected that running in Stackblitz is slower than locally because it will have to download the WebAssembly binary and then use that instead of using the native bindings.

0 replies

theshadowagent · 2024-10-04T10:22:04Z

theshadowagent
Oct 4, 2024
Author

@timneutkens thanks, I understand. Is WebAssembly build for Turbopack on the roadmap somewhere, or should I switch to server environment?

On WebAssembly binary: I've managed to reduce the time by 2x via adding @next/swc-wasm-nodejs to my package.json, but that only worked with [email protected]. [email protected] still downloads the binary (at least according to console) even if it's present in package.json.

Still, compile step takes about 10s, so WebAssembly build for Turbopack would be amazing.
See bolt.new for why it might be important

0 replies

timneutkens · 2024-10-04T11:11:00Z

timneutkens
Oct 4, 2024
Maintainer

We're currently focused on making sure that as many people as possible get the benefits of Turbopack, which means prioritizing development / builds with the native binding, after Turbopack development and build are stable we can investigate WebAssembly builds, though it's not straightforward to add this because of the premise of the compiler, which includes file watching, disk access (read/write) etc.

0 replies

theshadowagent · 2024-10-04T11:37:53Z

theshadowagent
Oct 4, 2024
Author

Got it, makes total sense! I think I'll switch to server VMs for now. I'm curious if this release helps to progress on this: https://deno.com/blog/rusty-v8-stabilized

0 replies

illegitimate-egg · 2024-10-29T08:20:52Z

illegitimate-egg
Oct 29, 2024

Bumping this, except for me rather than not working on stackblitz it doesn't work on my FreeBSD laptop

0 replies

ahmedkhabar · 2024-12-16T16:18:59Z

ahmedkhabar
Dec 16, 2024

Finally, I fix it - the solution was so simple: just upgrade the Node.js version using NVM with this command nvm install NEW_VERSION --reinstall-packages-from=OLD_VERSION and then I switch to the new Node version using nvm use 23.4.0 and change the version number "23.4.0" with the installed version.

Edit:
use lts instead because the latest version of Node js have some issues with prisma.
nvm install lts

0 replies

TonyRice · 2024-12-30T00:22:14Z

TonyRice
Dec 30, 2024

I'm currently running the next boilerplate on a termux install. I'm running the latest version of nodejs built for arm64

I get this same error on a fresh install for the boilerplate project.

0 replies

TonyRice · 2024-12-30T00:26:35Z

TonyRice
Dec 30, 2024

You can optionally disable turbo and use webpack.

0 replies

1sh4sk · 2025-01-05T08:30:07Z

1sh4sk
Jan 5, 2025

i ran into this error too i guess it happened because while creating the nextjs app some packages are not installed correctly what i did is delete the project and create it from the start and the error no longer exists

solution:
delete the nextjs project you just created
and create a new one from the start by using the command npx create-next-app@latest

0 replies

Badbird5907 · 2025-01-29T15:37:54Z

Badbird5907
Jan 29, 2025

Hi, I am getting this error with create-next-app@latest and next@latest (15.1.6).
I'm using Stackblitz's webcontainer.

Edit: can reproduce in stackblitz

0 replies

mhr1380 · 2025-02-01T12:13:28Z

mhr1380
Feb 1, 2025

I had the same issue, and this worked for me: 🚀
1️⃣ Delete the .next and node_modules folders 🗑️
2️⃣ Run npm install (or yarn install) 📦
3️⃣ Restart the development server 🔄

Hope this helps! ✨

0 replies

Sani071 · 2025-02-04T18:32:01Z

Sani071
Feb 4, 2025

I had the same issue, and this worked for me: 🚀 1️⃣ Delete the .next and node_modules folders 🗑️ 2️⃣ Run npm install (or yarn install) 📦 3️⃣ Restart the development server 🔄

Hope this helps! ✨

It worked for me.
Thanks @mhr1380

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

"next dev --turbo" fails in WASM with error (`turbo.createProject` is not supported by the wasm bindings) #75665

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 16 comments

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

"next dev --turbo" fails in WASM with error (turbo.createProject is not supported by the wasm bindings) #75665

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

Replies: 16 comments

samcx Oct 1, 2024 Maintainer

theshadowagent Oct 2, 2024 Author

theshadowagent Oct 2, 2024 Author

timneutkens Oct 4, 2024 Maintainer

theshadowagent Oct 4, 2024 Author

timneutkens Oct 4, 2024 Maintainer

theshadowagent Oct 4, 2024 Author

"next dev --turbo" fails in WASM with error (`turbo.createProject` is not supported by the wasm bindings) #75665

samcx
Oct 1, 2024
Maintainer

theshadowagent
Oct 2, 2024
Author

theshadowagent
Oct 2, 2024
Author

timneutkens
Oct 4, 2024
Maintainer

theshadowagent
Oct 4, 2024
Author

timneutkens
Oct 4, 2024
Maintainer

theshadowagent
Oct 4, 2024
Author