We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In case when we have for instance entry like below
code example №1
entry: { vendor: ['react', 'react-dom'], app: path.resolve(__dirname, './src/index.tsx'), }
React refresh does full reload for the page. but if we change the entry above on this with one entry
code example №2 entry: path.resolve(__dirname, './src/index.tsx')
entry: path.resolve(__dirname, './src/index.tsx')
Everything works as we are expecting - we have a local hot update at changed component without a full page refresh
A simple example of this problem can see here https://github.com/vovakulikov/sandbox - if add an entry to webpack.config.js like at code example №1 we will see a problem with a full refresh
The text was updated successfully, but these errors were encountered:
This should solve your problem :)
https://github.com/pmmmwh/react-refresh-webpack-plugin/blob/main/docs/TROUBLESHOOTING.md#component-not-updating-with-bundle-splitting-techniques
Sorry, something went wrong.
No branches or pull requests
In case when we have for instance entry like below
code example №1
React refresh does full reload for the page. but if we change the entry above on this with one entry
code example №2
entry: path.resolve(__dirname, './src/index.tsx')
Everything works as we are expecting - we have a local hot update at changed component without a full page refresh
A simple example of this problem can see here https://github.com/vovakulikov/sandbox - if add an entry to webpack.config.js like at code example №1 we will see a problem with a full refresh
The text was updated successfully, but these errors were encountered: