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
I love this package and the ability to hot reload components (and eventually styles!) on the client. It's saving me lots of development time.
That being said, every time I make a change to a shared file (which is ALL of my components to support SSR) it causes a full server reload and I can't interact with the server until the reload finishes, which for my app is around 30 seconds.
This got me thinking - is it possible to short-circuit the reload on the server and simply hot patch the server side as well?
The text was updated successfully, but these errors were encountered:
This is something I'd like to aim for in the long term. Two main problems I foresee:
We won't be able to replace the existing modules-runtime as easily. Will investigate other avenues to hack this but most likely will require putting a replacement modules-runtime in the app's packages dir.
Blocking the server reload... this would also be hard; might have to go back to our old way of tricking the bundler into thinking that nothing has changed... but then there's no fallback if we get something wrong (like how we just let the new bundle through on the client via HCP if HMR fails).
I love this package and the ability to hot reload components (and eventually styles!) on the client. It's saving me lots of development time.
That being said, every time I make a change to a shared file (which is ALL of my components to support SSR) it causes a full server reload and I can't interact with the server until the reload finishes, which for my app is around 30 seconds.
This got me thinking - is it possible to short-circuit the reload on the server and simply hot patch the server side as well?
The text was updated successfully, but these errors were encountered: