Better WASM fallback support for Turbopack

Hi!

Just wanted to leave some feedback about Turbopack’s WASM fallback.

I was trying to run a Next.js project inside Ubuntu on Termux(Android). Since the native Turbopack bindings aren’t available there, Next.js falls back to the WASM bindings, which is expected.

However, it immediately fails with:

 ✓ Starting... 
Skipping creating a lockfile at /root/Mail/.next/dev/lock because we're using WASM bindings
Error: \`turbo.createProject\` is not supported by the wasm bindings.

I know this isn’t a supported environment right now, so I’m not reporting this as a bug.

I’m just hoping WASM support can become more complete in the future. I don’t expect native-level performance—I just think it’d be nice if Turbopack could still run in environments where native bindings aren’t an option.

Thanks for all the work on Next.js!