This repository was archived by the owner on Mar 19, 2026. It is now read-only.
forked from vitejs/vite
-
-
Notifications
You must be signed in to change notification settings - Fork 19
This repository was archived by the owner on Mar 19, 2026. It is now read-only.
Update Rolldown to 1.0.0-rc.3 #609
Copy link
Copy link
Closed
Labels
Description
Describe the bug
I'm trying to integrate rolldown-plugin-dts with Typescript v6.0.0-beta, but the library require v1.0.0-rc.3 or later.
Reproduction
https://stackblitz.com/edit/vitejs-rolldown-vite-k5vcknek?file=vite.config.ts
Steps to reproduce
Run npm run build
System Info
System:
OS: Linux 5.0 undefined
CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Memory: 0 Bytes / 0 Bytes
Shell: 1.0 - /bin/jsh
Binaries:
Node: 20.19.1 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 10.8.2 - /usr/local/bin/npm
pnpm: 8.15.6 - /usr/local/bin/pnpm
npmPackages:
rolldown-vite: 7.3.1Used Package Manager
npm
Logs
Click to expand!
❯ npm run build --debug
> vite-starter@0.0.0 build
> vite build
(node:63) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:63) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
rolldown-vite v7.3.1 building client environment for production...
✗ Build failed in 4ms
thread '<unnamed>' (2) panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/napi-3.6.1/src/tokio_runtime.rs:113:6:
Access tokio runtime failed in spawn
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error during build:
RuntimeError: unreachable
at wasm://wasm/0283732e:wasm-function[17333]:0x870843
at wasm://wasm/0283732e:wasm-function[17229]:0x8705f3
at wasm://wasm/0283732e:wasm-function[17059]:0x87008b
at wasm://wasm/0283732e:wasm-function[17174]:0x870436
at wasm://wasm/0283732e:wasm-function[17173]:0x87042e
at wasm://wasm/0283732e:wasm-function[17228]:0x8705eb
at wasm://wasm/0283732e:wasm-function[1502]:0x4b5969
at wasm://wasm/0283732e:wasm-function[8823]:0x7cf82e
at wasm://wasm/0283732e:wasm-function[17041]:0x86ffc4
at wasm://wasm/0283732e:wasm-function[15185]:0x8634a7Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs and the Rolldown-related guide.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
Reactions are currently unavailable