-
-
Notifications
You must be signed in to change notification settings - Fork 36
Upcoming Release Changes #2406
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
Upcoming Release Changes #2406
Conversation
6aec55f
to
401e3bb
Compare
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
401e3bb
to
e45099c
Compare
e45099c
to
d03a751
Compare
✅
|
✅
|
✅
|
✅
|
✅
|
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@whatwg-node/[email protected]
Patch Changes
#2383
9527e8f
Thanks @ardatan! - Some implementations like
compression
npmpackage do not implement
response.write(data, callback)
signature, but whatwg-node/server waitsfor it to finish the response stream. Then it causes the response stream hangs when the
compression package takes the stream over when the response data is larger than its threshold.
It is actually a bug in
compression
package;expressjs/compression#46 But since it is a
common mistake, we prefer to workaround this on our end.
Now after calling
response.write
, it no longer uses callback but first it checks the result;if it is
true
, it means stream is drained and we can callresponse.end
immediately. else if itis
false
, it means the stream is not drained yet, so we can wait for thedrain
event to callresponse.end
.Updated dependencies
[
9527e8f
]:@whatwg-node/[email protected]
Patch Changes
#2383
9527e8f
Thanks @ardatan! - Some implementations like
compression
npmpackage do not implement
response.write(data, callback)
signature, but whatwg-node/server waitsfor it to finish the response stream. Then it causes the response stream hangs when the
compression package takes the stream over when the response data is larger than its threshold.
It is actually a bug in
compression
package;expressjs/compression#46 But since it is a
common mistake, we prefer to workaround this on our end.
Now after calling
response.write
, it no longer uses callback but first it checks the result;if it is
true
, it means stream is drained and we can callresponse.end
immediately. else if itis
false
, it means the stream is not drained yet, so we can wait for thedrain
event to callresponse.end
.Updated dependencies
[
d86b4f3
]:@whatwg-node/[email protected]
Patch Changes
d86b4f3
Thanks @slagiewka! - Reuse fake promise Symbol
@whatwg-node/[email protected]
Patch Changes
#2383
9527e8f
Thanks @ardatan! - Some implementations like
compression
npmpackage do not implement
response.write(data, callback)
signature, but whatwg-node/server waitsfor it to finish the response stream. Then it causes the response stream hangs when the
compression package takes the stream over when the response data is larger than its threshold.
It is actually a bug in
compression
package;expressjs/compression#46 But since it is a
common mistake, we prefer to workaround this on our end.
Now after calling
response.write
, it no longer uses callback but first it checks the result;if it is
true
, it means stream is drained and we can callresponse.end
immediately. else if itis
false
, it means the stream is not drained yet, so we can wait for thedrain
event to callresponse.end
.Updated dependencies
[
d86b4f3
,9527e8f
]:@benchmarks/[email protected]
Patch Changes
[
9527e8f
]:@e2e/[email protected]
Patch Changes
[
9527e8f
]:@e2e/[email protected]
Patch Changes
[
9527e8f
]:@e2e/[email protected]
Patch Changes