next.js
next.js copied to clipboard
fix: multi zone hmr
Bug
- [x] Related issues linked using fixes #32634
Hey! First time contributing to next.js 😊 If there is something missing let me know and I can work on it!
We were having exactly this problem in our company, great solution!
Hey, I don't mean to bother any of the reviewers, I guess you guys are all really occupied. Please if anyone can review this it would be great :) Thanks!
EDIT: Maybe Im a little bit anxious, but I really don't know whats the average time for a new contributor to get a review 😅
Would be good to see this merged soon. We have the same issue with multizones and we can't upgrade to version 12 😢
We are in the same boat. Would love to see this released
🙃
So the problem with not allowing something like this through is that you advertise multi zones
which is awesome except you can't enjoy the HMR
features cause the websocket requests can't be proxied "out-of-the-box". If you decide to go with this route, which is totally fine, I recommend on your docs to add a side note saying that HMR
doesn't work and a code snippet showing the workaround using a custom server.
Is it possible to let the user handle websocket requests inside middleware in the future?