Issue with adding/removing hooks when runtimeChunk is true
See original GitHub issueWhen runtimeChunks: true
is enabled in the webpack config, I’m running into an issue with getting Rendered more hooks than during the previous render.
(or less, depending on what hooks get added/removed). To reproduce, add optimization: { runtimeChunks: true }
to the webpack config of wds-kitchen-sink
, and then add a hook to a functional component, save, and add another, The error should appear.
Edit - what I originally thought was incorrect 😦
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Optimization - webpack
When set to true tells webpack to reduce the size of WASM by changing imports to shorter strings. It mangles module and export...
Read more >react-refresh-webpack-plugin - Bountysource
I need to install react devtools hook (not from the devtools extension) before the reach ... I'm running into issues getting hot reloading...
Read more >Webpack 5 module federation - hooks in remote module
Fixed it for me when hooks broke my host app. It's because there are duplicate react dependencies, regardless if the version are the...
Read more >gatsby @ 2.1.4 .. 2.1.27 - Package Diff
+ // Hooks for gatsby-cypress's API handler ... __navigatingToLink = true; ... after bootstrap ([#12262](https://github.com/gatsbyjs/gatsby/issues/12262)) ...
Read more >@wordpress/eslint-plugin: Versions | Openbase
Comments: Fix issue with custom font sizes and links color. ... Draggable: Add clarifying inline comment after the recent hook dependency changes.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed in
v0.1.3
🎉Thank you!!