Repository navigation
fix(deps): update dependency @whatwg-node/server to v0.13.1 - #3183
Merged
Merged
Conversation
✅ Deploy Preview for cedarjs canceled.
|
|
| Command | Status | Duration | Result |
|---|---|---|---|
nx run-many -t test --maxWorkers=4 |
✅ Succeeded | 5m 31s | View ↗ |
nx run-many -t build:pack --exclude create-ceda... |
✅ Succeeded | 4s | View ↗ |
nx run-many -t build --output-style=stream |
✅ Succeeded | 6s | View ↗ |
nx run-many -t test:types |
✅ Succeeded | 18s | View ↗ |
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗
☁️ Nx Cloud last updated this comment at 2026-10-26 07:27:23 UTC
|
The changes in this PR are now available on npm. Try them out by running Or try it in a new app with |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

This PR contains the following updates:
0.13.0→0.13.1Release Notes
ardatan/whatwg-node (@whatwg-node/server)
v0.13.1Compare Source
Patch Changes
#3672
978ebedThanks @renovate! - Drain unread request
bodies correctly when the adapter uses the platform (native undici)
Requeston Node.js HTTPS.
discardUnreadNodeRequestBodypreviously only calledIncomingMessage#resume(). That is enough for the@whatwg-node/node-fetchponyfill and for plain
node:http, but native undici keeps an unusedIncomingMessagebody paused. Onnode:httpsthe TLS upload then stallsmid-response:
readableFlowingstays false, buffered unread bytes remain, andkeep-alive / early-response paths hang or fail Node 26 unit coverage
(
discard-unread-request-body).For
fetchAPI.Request === globalThis.Requeston HTTPS(
socket.encrypted),normalizeNodeRequestwraps the socket stream in aplatform
ReadableStream(viafetchAPI.ReadableStream). Listeners attach onfirst pull; discard runs a sync drain helper (detach +
IncomingMessage#resume) instead ofbody.cancel(), so unread TLS bytesdrain without destroying keep-alive and without a runtime
node:stream/PassThroughimport or a floating cancel promise. Plain HTTP and ponyfillpaths are unchanged (
IncomingMessage+resume()only). Paths that reuserequest.bodyas the response body still skip discard via the existingidentity checks.
#3717
02e1834Thanks @ardatan! - Pick the native Fetch API for
Requestsubclasses and proxies of them, such as Next.jsNextRequest.Constructor identity treated those requests as the ponyfill, so
useLimitRequestBodySizepiped a native body throughPonyfillTransformStreamand Node threwThe "transform.readable" property must be an instance of ReadableStream.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.