Open acnebs opened 1 week ago
Hello @acnebs, 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.
System Info
System: OS: macOS 14.5 CPU: (8) arm64 Apple M1 Memory: 174.95 MB / 16.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 18.20.2 - ~/.nvm/versions/node/v18.20.2/bin/node pnpm: 8.15.7 - ~/.nvm/versions/node/v18.20.2/bin/pnpm npmPackages: @rspack/cli: ^0.7.3 => 0.7.3 @rspack/core: ^0.7.3 => 0.7.3 @rspack/dev-server: ^0.7.3 => 0.7.3 @rspack/plugin-react-refresh: ^0.7.3 => 0.7.3 fork-ts-checker-webpack-plugin: ^9.0.2 => 9.0.2
Details
When using fork-ts-checker-webpack-plugin with rspack, I get frequent errors (about 50% of the time it seems) related to process communication. Error looks like this:
Whether or not it works is incredibly random. I will try to start the dev server and it will fail, and then (with no code changes) I will try again and it will work. It seems to be slightly less likely to fail after repeated attempts, and most likely to fail if I haven't built in a while. Same thing happens when building with rspack.
Reproduce link
No response
Reproduce Steps
Unknown. But happens in our code-base quite frequently but randomly.