You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disable fast refresh for when an environment or toolkit is not compatible with it.
As a general rule, a framework should not get into a developer's hair.
Non-Goals
Encourage people to disable it permenently, so maybe add a warning in the console to encourage folks to turn it back on.
Background
Testing any website through local testing, in development mode, on any BrowserStack machine, will break the whole website with a WSOD, and an error in the console about fast refresh.
As a developer trying to get to an issue on a specific browser, I don't want to be thrown into the rabbit hole of trying to get fast refresh to work on a browser that essentially isn't mine. I just need it to get out of my way, at least for the moment, so that I can get to the page where I can debug the issue at hand and just do my work.
Maybe I just don't have time to dive into why FR isn't working, and maybe I don't need it to work for the issue I'm trying to solve. And maybe it's just really frustrating when a framework is creating a problem for me that is hindering me from doing my work.
Proposal
A environment variable, or a switch in next.config.js.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
Non-Goals
Background
Testing any website through local testing, in development mode, on any BrowserStack machine, will break the whole website with a WSOD, and an error in the console about fast refresh.
As a developer trying to get to an issue on a specific browser, I don't want to be thrown into the rabbit hole of trying to get fast refresh to work on a browser that essentially isn't mine. I just need it to get out of my way, at least for the moment, so that I can get to the page where I can debug the issue at hand and just do my work.
Maybe I just don't have time to dive into why FR isn't working, and maybe I don't need it to work for the issue I'm trying to solve. And maybe it's just really frustrating when a framework is creating a problem for me that is hindering me from doing my work.
Proposal
A environment variable, or a switch in next.config.js.
Beta Was this translation helpful? Give feedback.
All reactions