Describe the bug
When starting a new project:
~/projects/vitejs-vite-c9ucu57i
❯ npm install && npm run dev
added 154 packages in 3s
43 packages are looking for funding
run `npm fund` for details
> vite-react-typescript-starter@0.0.0 dev
> vite
[rolldown] Downloading @rolldown/binding-wasm32-wasi@1.0.3 on WebContainer...
Packages: +7
+++++++
Progress: resolved 7, reused 0, downloaded 7, added 7, done
dependencies:
+ @rolldown/binding-wasm32-wasi 1.0.3 (1.1.1 is available)
Done in 7.9s
(node:12) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:12) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
worker (tid = 43) sent an error! Invalid atomic access index
RangeError: Invalid atomic access index
at Object.storeSizeTypeValue (/tmp/rolldown-1.0.3/node_modules/.pnpm/@emnapi+core@1.10.0/node_modules/@emnapi/core/dist/emnapi-core.cjs.js:1218:29)
at Object.pushQueue (/tmp/rolldown-1.0.3/node_modules/.pnpm/@emnapi+core@1.10.0/node_modules/@emnapi/core/dist/emnapi-core.cjs.js:990:28)
at eval (/tmp/rolldown-1.0.3/node_modules/.pnpm/@emnapi+core@1.10.0/node_modules/@emnapi/core/dist/emnapi-core.cjs.js:1040:36)
at Object.execute (/tmp/rolldown-1.0.3/node_modules/.pnpm/@emnapi+core@1.10.0/node_modules/@emnapi/core/dist/emnapi-core.cjs.js:1094:36)
at Object.push (/tmp/rolldown-1.0.3/node_modules/.pnpm/@emnapi+core@1.10.0/node_modules/@emnapi/core/dist/emnapi-core.cjs.js:1029:33)
at napi_call_threadsafe_function (/tmp/rolldown-1.0.3/node_modules/.pnpm/@emnapi+core@1.10.0/node_modules/@emnapi/core/dist/emnapi-core.cjs.js:1612:31)
Node.js v22.22.0
~/projects/vitejs-vite-c9ucu57i 17s
Link to the blitz that caused the error
https://stackblitz.com/edit/vitejs-vite-c9ucu57i?file=src%2Fcontext.tsx&terminal=dev
Steps to reproduce
- Start a new project with the React TypeScript template
Expected behavior
Not that :-)
I have not tried to run this locally
Parity with Local
Screenshots
No response
Platform
Browser name = Chrome
Full version = 149.0.0.0
Major version = 149
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36
performance.memory = {
"totalJSHeapSize": 47769802,
"usedJSHeapSize": 44137398,
"jsHeapSizeLimit": 4395630592
}
Hash = bd880c29
Additional context
No response
Describe the bug
When starting a new project:
Link to the blitz that caused the error
https://stackblitz.com/edit/vitejs-vite-c9ucu57i?file=src%2Fcontext.tsx&terminal=dev
Steps to reproduce
Expected behavior
Not that :-)
I have not tried to run this locally
Parity with Local
Screenshots
No response
Platform
Additional context
No response