[Bug]: Panic occurred at runtime: "should have module" (new_code_splitter.rs:750)

[josiahbryan]

System Info

System:
OS: macOS 15.5
CPU: (12) arm64 Apple M2 Max
Memory: 228.97 MB / 96.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.17.0 - ~/.nvm/versions/node/v20.17.0/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 10.8.2 - ~/.nvm/versions/node/v20.17.0/bin/npm
pnpm: 9.15.3 - /usr/local/bin/pnpm
Browsers:
Chrome: 137.0.7151.122
Safari: 18.5
npmPackages:
@rspack/plugin-react-refresh: ^1.0.1 => 1.4.3

Details

 @ ./src/index.js

start   building pages/notifications/NotificationsPage.js
ready   built in 4.67 s
start   building pages/notifications/NotificationsPage.js
ready   built in 5.92 s
start   building pages/notifications/NotificationsPage.js
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/build_chunk_graph/new_code_splitter.rs:750

Backtrace omitted.

Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

Reproduce link

No response

Reproduce Steps

Use Cursor to change a lot of files lol

[JSerFeng]

There is some modules missing in the seal.

Try use config bail: true to see if something goes wrong before seal

[yf-yang]

@JSerFeng I also encountered similar problem when using rsbuild+react routers, in dev mode, when saving files. Rspack sometimes panic with this message and sometimes panic with "should have target module". RUST_BACKTRACE=full shows no backtrace. Tried to enable tracing but didn't find something useful. Enabling bail: true does not show any more output.

This problem happens both in MacOS and Linux container. I observe high memory usage, but seems it is not related.

Now since this problem is very likely to happen, but I cannot reproduce that with a small repo. Are there any other way I can provide possibly related information to you?