4 ms·
I guess Im different to most JS developers, because I prefer to work with HMR off about 95% of the time. Its good for UI prototyping (which I dont do much tbf),
by dreen 6y ago
I guess Im different to most JS developers, because I prefer to work with HMR off about 95% of the time. Its good for UI prototyping (which I dont do much tbf), but it tends to get in my way when doing anything else. Maybe in total it makes me loose a minute or two but thats not an issue.
- Etheryte 6y agoThis is interesting, what's the upside of working without HMR? There are changes where HMR fails to figure things out and you have to hard reload, but other than those it has served me very well otherwise. Interested in hearing the other side of the story, if there is one.
- dreen 6y agoHard reload takes marginally longer, but has no potential to fail - its peace of mind. I have had cases when small changes to dev tooling or maybe something in state management causes a failure during HMR reload. And if you dont realise this quickly enough, you might waste a lot more time than HMR saves you. As I said its still quite useful for working just on UI, so its not all bad, but ideally I prefer to work on UI components separately to the app anyway, eg using something like Storybook.