-
Notifications
You must be signed in to change notification settings - Fork 3
Improve DX by implementing Hot Module Replacement (HMR) for React #219
Comments
Ambiguous title in feature request (DX = developer experience).
|
What's current status on this? I'm working on a very large Meteor project and would truly appreciate having HMR. I recently worked on a Node project that had it, and I have to say it is a total game changer. |
+1 this is really needed we're having on average a 15 seconds refresh time |
The refresh time has been improved significantly with the latest meteor releases and the separation of Meteor client/server watchset. However I do think this module.accept() API is useful to have and standardize in the bundlers ecosystem. Furthermore, the react team is working on implementing a more reliable fast refresh feature which is a good opportunity for Meteor to support hot reload out of the box. |
This is still a highly needed feature. For our setup, rebuilds are still sluggish. |
Same for us, it's unbearable. |
I think that adding HMR support to Meteor's build system will be an incredible feature, because it directly improves Developer's productivity.
I envy my colleagues that uses Next.js to build their frontend because, while I need to wait for a full page refresh, they just save changes and see results instantly.
The text was updated successfully, but these errors were encountered: