-
-
Notifications
You must be signed in to change notification settings - Fork 531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Panic occurred at runtime,using @rspack/[email protected] #6486
Comments
@jerrykingxyz This panic seems related to incremental rebuild, after add |
@childrentime WebpackDemandEntryPlugin seems can be replaced by lazyCompilation, lazyCompilation can also compile other unused entries lazily, we will release lazyCompilation in v0.7.0 (in this week if all goes well, for now you can try 0.7.0-beta.0-canary-633b9cb-20240520070628) |
@ahabhgk How does lazyCompilation compile the corresponding client entry when accessing the route? I can understand that it can be done on the server side. |
https://webpack.js.org/configuration/experiments/#experimentslazycompilation there is |
seems fixed in rspack v0.7.1 |
sorry. I accidentally misread it. |
Issue still occurs in 1.0.0 alpha. Below is my config
Occurs when running rspack server with NODE_ENV set to development. Sometimes, went updating the components, the HMR seems to cause it to crash with the following error:
|
Hello @childrentime, 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 |
@AdamJSoftware Please provide a repro repo. |
Not sure what I did but the issue disappeared... If it comes back up again I'll create a repro repo |
Since the issue was labeled with |
System Info
System:
OS: macOS 14.1
CPU: (8) arm64 Apple M3
Memory: 92.16 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
Yarn: 1.22.21 - ~/.nvm/versions/node/v18.12.1/bin/yarn
npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
pnpm: 8.15.5 - ~/.nvm/versions/node/v18.12.1/bin/pnpm
Watchman: 2024.04.15.00 - /opt/homebrew/bin/watchman
Browsers:
Chrome: 124.0.6367.119
Edge: 124.0.2478.80
Safari: 17.1
Details
Hello, I am currently developing a streaming rendering framework based on rspack. I noticed that the latest version of rspack supports dynamic entries, so I am trying to use it.
When I start running my application, everything works fine when I access the /home route. However, when I then access the /user route, the following error occurs. It's not an issue with a specific route, because the same problem occurs when I first access the /user route and then the /home route.
trace stack:
Reproduce link
https://github.com/childrentime/pareto
Reproduce Steps
pnpm i cd examples/lazy-route pnpm dev
visit http://localhost:4000/home
visit http://localhost:4000/user
The text was updated successfully, but these errors were encountered: