next.js
a025b5b2 - fix(turbo-rcstr): allow the napi feature on wasm targets

Commit

13 hours ago

fix(turbo-rcstr): allow the napi feature on wasm targets napi v3 supports wasm32-wasip1-threads, so the hard compile_error! rejecting the combination is obsolete. Removing it, turbo-rcstr/napi and everything built on it (turbopack-node/worker_pool, next-api/worker_pool, next-napi-bindings) compiles for wasm. Co-authored-by: Luke Sandberg <210140+lukesandberg@users.noreply.github.com>

References

codex/turbopack-wasm/rcstr-napi-feature

#97578 - fix(turbo-rcstr): allow the napi feature on wasm targets

#97579 - fix(turbo-tasks): compile EventListener::wait on wasm

#97580 - fix(turbo-tasks-fs): create symlinks through the WASI API on wasi

#97581 - refactor(turbopack-cli-utils): replace crossterm with owo-colors

#97582 - fix(turbopack-trace-utils): skip the ctrl-c handler on wasm

#97583 - fix(turbopack): make the SWC wasm-plugin backend native-only

#97584 - fix(turbopack-node): make process_pool inert on wasm

#97585 - feat(turbo-tasks-fetch): stub HTTP on wasm targets

#97586 - feat(next-napi-bindings): build Turbopack for wasm

#97587 - build: add an opt-in patch for swc's wasm32 plugin host