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
Hello, I have an expressjs back-end and a Vite dev server (running React) on the front-end. Have you encountered the issue where the close event from the client doesn't get triggered? I've inquired with Vite and with one of their dependency libraries, node-http-proxy. I don't think this is an issue with your library, it's lower level and probably with one of those 3rd parties but thought I'd ask.
I am not using this library, so it may be wrong to write here, but I was encountering the same problem as you, so I share the information.
I am using Go for the back-end, but the front-end is the same (running React on a vite dev server).
The close event of the client was not propagated to the back-end.
I added the following settings to vite.config.ts based on the comments you provided(http-party/node-http-proxy#921 (comment)), and now the close event is propagated to the back-end.
(The version of vite I am using is 4.3.0)
Hello, I have an expressjs back-end and a Vite dev server (running React) on the front-end. Have you encountered the issue where the
close
event from the client doesn't get triggered? I've inquired with Vite and with one of their dependency libraries, node-http-proxy. I don't think this is an issue with your library, it's lower level and probably with one of those 3rd parties but thought I'd ask.http-party/node-http-proxy#921 (comment)
vitejs/vite#12157 (contains link to demo for the issue)
The text was updated successfully, but these errors were encountered: