frontend/vite-shopify-storefront
Template
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Stop depending on @rolldown/binding-wasm32-wasi directly

Browse Source 
The binding declares cpu: wasm32, so npm on x64 hosts (Vercel) fails
with EBADPLATFORM. The nodesandbox runtime already installs every
package's *-wasm32-wasi optional dependency (rolldown's included), so
the app doesn't need to list it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Rami Bitar
2026-10-03 15:16:59 -04:00
co-authored by Claude Opus 5.5
parent fb7ef27621
commit d33a6894f3
3 changed files with 8 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+8 -4
View File
@@ -27,10 +27,14 @@ yarn dev # http://localhost:3000
The sandbox runs Vite's native tools as WebAssembly (`NAPI_RS_FORCE_WASI`), and
its installer resolves from `package.json` ranges rather than `yarn.lock`. So:
- `vite` is pinned to **8.1.3**, which uses rolldown 1.1.x; `rolldown` and
`@rolldown/binding-wasm32-wasi` are pinned to **1.1.4**. Rolldown 1.2.x's
WASI binding needs glue the runtime doesn't support ("WASI binding not
found"). Bump these only together with the runtime.
- `vite` is pinned to **8.1.3**, which uses rolldown 1.1.x, and `rolldown` to
**1.1.4**. Rolldown 1.2.x's WASI binding needs glue the runtime doesn't
support yet ("WASI binding not found"). Bump these only together with the
runtime.
- WASI bindings (`@rolldown/binding-wasm32-wasi`, `@tailwindcss/oxide-wasm32-wasi`)
are **not** listed here: the runtime installs each package's `*-wasm32-wasi`
optional dependency itself, and npm on other hosts rejects them
(`EBADPLATFORM`).
- `@vitejs/plugin-react` (6.0.0) and Tailwind (4.3.1) match the harness samples.
- No Nitro: it brings its own rolldown 1.2.x.