Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add compatibility with React Fast Refresh
See original GitHub issueIs your feature request related to a problem? Please describe.
react-refresh is the successor for react-hot-loader
While using Fast Refresh on a project, changes in the theme don’t trigger HMR. Which make sense, since it’s supposed to preserve the context and states.
Describe the solution you’d like It would be nice to find a way, to have HMR work on theme changes, while using this feature. Not sure how we could go around this.
Describe alternatives you’ve considered
We could mention, the compatibility issue in the docs.
Gatsby now has a FAST_REFRESH flag, which makes it easy to break theme HMR.
Additional context You can test this out on a repro I did for another issue.
- Simply set the Fast Refresh flag to true
// gatsby-config.js
flags: {
FAST_REFRESH: true,
},
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Essentially, without Fast Refresh, changes trigger full reload (logs above). But when using Fast Refresh, changes to the theme don’t trigger anything at all. No full reload nor HMR.
The same thing happens when the theme lives in
gatsby-plugin-theme-ui.That theme/index.js is just a big JavaScript object with a bunch of colors and styles inside, right? How does that conflict with Fast Refresh?