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 don't know if it's supposed to be a feature or a bug, so I'm opening this here and we can escalate if need be (I think it could be fixed)
With a codebase containing a folder /api, HMR natively reload using the fs path /api/index.ts when a change occured. this works great unless you also define a /api proxy.
When doing so, the proxy will take precedence over the HMR and break HMR.
Is it supposed to be like this? Do we have to handle HMR in userland (vite.config) or is it a bug?
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
-
I don't know if it's supposed to be a feature or a bug, so I'm opening this here and we can escalate if need be (I think it could be fixed)
With a codebase containing a folder
/api
, HMR natively reload using the fs path/api/index.ts
when a change occured. this works great unless you also define a/api
proxy.When doing so, the proxy will take precedence over the HMR and break HMR.
Is it supposed to be like this? Do we have to handle HMR in userland (vite.config) or is it a bug?
Beta Was this translation helpful? Give feedback.
All reactions