Provide a way to disable Fast Refresh and fallback to classic browser reload.
See original GitHub issueHi,
Recently upgraded to CRA 4 and it’s great so far. Well, almost great. While the new fast refresh works great on our landing pages, it does not work on our core app. The issue is that our core app relies heavily on events and js canvas, and that’s where fast refresh does not work well, or at all.
Is there a way to optionally disable the fast refresh and fallback to browser reload on file save/update? I tried adding FAST_REFRESH=false
env but it did not work.
Thanks in advance.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:13 (1 by maintainers)
Top Results From Across the Web
How to disable `Fast Refresh` in React native on Javascript ...
Fast Refresh is broken in some Detox tests and I need to disable it from Javascript, without using the Developer Menu. Any idea?...
Read more >Basic Features: Fast Refresh - Next.js
Next.js' Fast Refresh is a new hot reloading experience that gives you instantaneous feedback on edits made to your React components.
Read more >Development - Parcel
As you make changes to your code, Parcel automatically rebuilds the changed files and updates your app in the browser. By default, Parcel...
Read more >React Suspense in Practice | CSS-Tricks
React will look up the tree, find the first <Suspense> component, and render its fallback. I'll be providing plenty of examples, ...
Read more >Microsoft Edge Browser Policy Documentation
You can use these policies to configure how Microsoft Edge runs in your ... Dynamic Policy Refresh: No - Requires browser restart ......
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
#9884 fixed this three weeks ago. Not sure why the delay to push this fix and others.
Could it be possible to disable by default this experimental feature? Only activated by devs when
FAST_REFRESH
is really desired and useful…