You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rsbuild build panics with the error bellow when project is placed in a directory with a long path on windows. We also use pnpm
Rsbuild v1.0.16
● web ━━━━━━━━━━━━━━━━━━━━━━━━━ (63%) building commonjs|C:\Users\xxxxxx.xxxxxxxxxx.xxxxxxxxx\Projects\xxxxxxxxxxxxx\src\Syn...
Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message: should have module
Location: crates\rspack_core\src\compiler\module_executor\execute.rs:81
Moving project to the root directory fixes the issue. If the error can't be eliminated there should at least be a better error message.
Reproduce link
No response
Reproduce Steps
Tried to reproduce it with https://github.com/web-infra-dev/rspack-repro by placing it in a path with a long name, but couldn't. It might be caused by a combination of pnpm symlinks with deeply nested packages and a long base directory name.
The text was updated successfully, but these errors were encountered:
System Info
System:
OS: Windows 11 10.0.22631
CPU: (16) x64 Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz
Memory: 14.51 GB / 31.85 GB
Binaries:
Node: 20.15.1 - C:\Program Files\nodejs\node.EXE
npm: 10.7.0 - C:\Program Files\nodejs\npm.CMD
pnpm: 9.9.0 - ~\AppData\Roaming\npm\pnpm.CMD
Browsers:
Chrome: 130.0.6723.117
Edge: Chromium (127.0.2651.74)
Internet Explorer: 11.0.22621.3527
npmPackages:
@rspack/core: ^1.0.14 => 1.0.14
Details
rsbuild build
panics with the error bellow when project is placed in a directory with a long path on windows. We also usepnpm
Moving project to the root directory fixes the issue. If the error can't be eliminated there should at least be a better error message.
Reproduce link
No response
Reproduce Steps
Tried to reproduce it with https://github.com/web-infra-dev/rspack-repro by placing it in a path with a long name, but couldn't. It might be caused by a combination of pnpm symlinks with deeply nested packages and a long base directory name.
The text was updated successfully, but these errors were encountered: