-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proxy request.signal through in vite dev #9976
Conversation
🦋 Changeset detectedLatest commit: 0689ce9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
It's working better now! But I'm still having issues with the signal not being aborted sometimes. Referencing this: sergiodxa/remix-utils#317 (comment) |
Is there a workaround for this? Maybe check every once is a while if a connection is closed to abort that connection? I'm having the same issue with node and the updated version of remix in production too.
|
It seems like the signal is working correctly until a new undici |
Possible fix: #10030 |
I am running into the same issue, and cannot get any EventSource to close with request.signal. Is there a workaround for how to handle this? Right now it is a huge block for developing with SSE. We have to restart the whole app constantly. |
v2.12.1 includes remix-run/remix#9976, which changed the API contract of the fromNodeRequest util that we will depend on in superflareDevProxyVitePlugin
Found this wasn't working right while testing #9975. Aligned with how we do it in the express adapter.
Closes #9438