[Bug]: Rspack 1.7.3 panicked at crates/rspack_core/src/utils/deref_option.rs:

[Amnesthesia]

System Info

System:
OS: macOS 26.1
CPU: (11) arm64 Apple M3 Pro
Memory: 191.83 MB / 18.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.14.0 - ~/.asdf/installs/nodejs/22.14.0/bin/node
Yarn: 4.9.2 - /opt/homebrew/bin/yarn
npm: 10.9.2 - ~/.asdf/plugins/nodejs/shims/npm
Browsers:
Safari: 26.1
npmPackages:
@rspack/cli: 1.7.3 => 1.7.3
@rspack/core: 1.7.3 => 1.7.3
@rspack/plugin-react-refresh: 1.6.0 => 1.6.0

Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues: panicked at crates/rspack_core/src/utils/deref_option.rs:47:26:
should set in compilation first

Details

Crashed after saving a couple of files, rebuilding and typechecking

Reproduce link

No response

Reproduce Steps

No clue why. It doesn't normally crash. After starting it again, I'm getting:

Error: Process 31799 doesn't have open IPC channels
node_modules/ts-checker-rspack-plugin/lib/getIssuesWorker.js:42:25
at new Promise ()
at sendMessage (node_modules/ts-checker-rspack-plugin/lib/getIssuesWorker.js:37:36)
at process.handleMessage (node_modules/ts-checker-rspack-plugin/lib/getIssuesWorker.js:61:28)

[n0th1ng-else]

could be, in fact, related to what I observe. at least the rust panic is the same

• [Bug]: Rspack 1.7.2 panicked with "should set in compilation first" #12785

[github-actions]

Hello @Amnesthesia, sorry we can't investigate the problem further without reproduction demo, please provide a repro demo by forking rspack-repro, or provide a minimal GitHub repository by yourself. Issues labeled by need reproduction will be closed if no activities in 14 days.

[hardfist]

@Amnesthesia can you help check whether this is fixed in 1.7.4

[Amnesthesia]

@hardfist I have no idea how to reproduce this, it just happened randomly once and I didnt get it again

[hardfist]

@Amnesthesia I think it's mostly related to #12785 and should be solved at 1.7.4