Description
Describe the bug
thread 'tokio-runtime-worker' panicked at /Users/runner/work/rolldown/rolldown/crates/rolldown/src/ecmascript/format/umd.rs:53:6:
iife format only have entry chunk
stack backtrace:
0: 0x10f7ca1b4 - _napi_register_module_v1
1: 0x10f118b9c -
2: 0x10f7c8aa8 - _napi_register_module_v1
3: 0x10f7ca074 - _napi_register_module_v1
4: 0x10f7c86bc - _napi_register_module_v1
5: 0x10f7f0f6c - _napi_register_module_v1
6: 0x10f7f0edc - _napi_register_module_v1
7: 0x10f7f1778 - _napi_register_module_v1
8: 0x10f853a3c - _napi_register_module_v1
9: 0x10f853e08 - _napi_register_module_v1
10: 0x10ee9fe74 -
11: 0x10eeaa3e8 -
12: 0x10f056c1c -
13: 0x10f058afc -
14: 0x10f04d930 -
15: 0x10f062238 -
16: 0x10f05d77c -
17: 0x10f060ac0 -
18: 0x10f0a7718 -
19: 0x10ef5a114 -
20: 0x10efc6a1c -
21: 0x10f8081f8 - _napi_register_module_v1
22: 0x10f806550 - _napi_register_module_v1
23: 0x10f80f218 - _napi_register_module_v1
24: 0x10f7fe858 - _napi_register_module_v1
25: 0x10f80bce8 - _napi_register_module_v1
26: 0x10f7f1a28 - _napi_register_module_v1
27: 0x19f306c0c - __pthread_cond_wait
✗ Build failed in 3.20s
error during build:
Panic in async function
Error: Panic in async function
ELIFECYCLE Command failed with exit code 1.
Reproduction
https://github.com/whg4/rolldown-svelte-demo
Steps to reproduce
vite build
System Info
System:
OS: macOS 15.5
CPU: (10) arm64 Apple M2 Pro
Memory: 93.70 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.20.4 - ~/Library/pnpm/node
npm: 10.7.0 - ~/Library/pnpm/npm
pnpm: 9.7.1 - ~/Library/pnpm/pnpm
bun: 1.2.2 - ~/.bun/bin/bun
Browsers:
Chrome: 137.0.7151.56
Safari: 18.5
Safari Technology Preview: 18.4
npmPackages:
@vitejs/plugin-legacy: ^6.0.2 => 6.1.1
@vitejs/plugin-vue: ^5.2.4 => 5.2.4
rolldown-vite: 6.3.17Used Package Manager
pnpm
Logs
No response
Validations
- 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.