fix(dev-overrides): Add automatic response cleanup via onClose callback #952
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To make
request.signal.onabort
work in route handlers. Currently only works fornode
andexpress-dev
. It will close theOpenNextNodeResponse
we pass intoNextServer
's request handler when the original response in the wrapper is closed. This will ensure that the AbortSignal associated withrequest.signal
is properly triggered when a client disconnects during a streaming response.I did try to get it to work with
awsLambda.streamifyResponse
. It looks like we get no event emitted onresponseStream
when a client disconnects. I even tried with a barebone Lambda like this: