4.0.0-next.77: fast refresh issues
See original GitHub issueI’m going to apologize up front for the lack of reproduction steps, but this is “feedback” in the most general sense.
I’ve been using “react-scripts”: “4.0.0-next.77” for the last three days. It’s been interesting. At it’s best it’s quite amazing and does exactly what you might want. But at its worst, it has been rather surprising.
I’ve seen lots of cases where some code that’s imported by a component changes, but the UI doesn’t notice. Not the end of the world, but refreshing the browser generally loads the correctly updated component. This can be particularly subtle since other things change and you know that things must have been reloaded, but in fact only some of the changes reach the browser. I should add that there are no class components in the code that I’m editing, they are all functional components. It is definitely true that at least some of the changes that aren’t being picked up are in shared utility functions and not in components themselves.
More frustrating is where you substantially change a file, especially if it’s been failing to compile for a while. You get it compiling and the browser can’t load it. You can refresh the browser as much as you like, but all it’s going to do it keep reporting the same compilation error. The only work around that I’ve found for this is to kill and restart yarn start
.
I’ll see if I can create reproduction steps for both of these, but I felt that it was worth giving feedback anyway since this is still alpha.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:6
Top GitHub Comments
My project also doesn’t work correctly after the update. it can’t update my reducers in redux
This issue has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue.