Sourced from @​whatwg-node/fetch's changelog.

0.10.7

Patch Changes

• #2383 9527e8f Thanks @​ardatan! - Some implementations like compression npm package do not implement response.write(data, callback) signature, but whatwg-node/server waits for 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 call response.end immediately. else if it is false, it means the stream is not drained yet, so we can wait for the drain event to call response.end.

• Updated dependencies [9527e8f]:

  • @​whatwg-node/node-fetch@​0.7.19

• 65780bc Upcoming Release Changes (#2406)
• See full diff in compare view

Sourced from @​whatwg-node/node-fetch's changelog.

0.7.19

Patch Changes

• #2383 9527e8f Thanks @​ardatan! - Some implementations like compression npm package do not implement response.write(data, callback) signature, but whatwg-node/server waits for 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 call response.end immediately. else if it is false, it means the stream is not drained yet, so we can wait for the drain event to call response.end.

• Updated dependencies [d86b4f3]:

  • @​whatwg-node/promise-helpers@​1.3.2

• 65780bc Upcoming Release Changes (#2406)
• 9527e8f fix(server): do not wait for response.write for response.end (#2383)
• See full diff in compare view

Sourced from @​whatwg-node/promise-helpers's changelog.

1.3.2

Patch Changes

• #2408 d86b4f3 Thanks @​slagiewka! - Reuse fake promise Symbol

• 65780bc Upcoming Release Changes (#2406)
• d86b4f3 refactor(promise-helpers): reuse promise Symbol (#2408)
• 9527e8f fix(server): do not wait for response.write for response.end (#2383)
• See full diff in compare view

Sourced from @​whatwg-node/server's changelog.

0.10.6

Patch Changes

• #2383 9527e8f Thanks @​ardatan! - Some implementations like compression npm package do not implement response.write(data, callback) signature, but whatwg-node/server waits for 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 call response.end immediately. else if it is false, it means the stream is not drained yet, so we can wait for the drain event to call response.end.

• Updated dependencies [d86b4f3, 9527e8f]:

  • @​whatwg-node/promise-helpers@​1.3.2
  • @​whatwg-node/fetch@​0.10.7

• 65780bc Upcoming Release Changes (#2406)
• 9527e8f fix(server): do not wait for response.write for response.end (#2383)
• 0ee2bbf fix(deps): update all non-major dependencies (#2401)
• 9bdd082 fix(deps): update dependency @​types/node to v22.15.15 (#2398)
• 5e8daec fix(deps): update all non-major dependencies (#2391)
• a48382f fix(deps): update all non-major dependencies (#2385)
• 85b11ad chore(deps): update dependency koa to v3 (#2353)
• e11b324 fix(deps): update dependency @​types/node to v22.15.3 (#2355)
• 90709cf fix(deps): update all non-major dependencies (#2351)
• 73e515c fix(deps): update all non-major dependencies (#2350)
• Additional commits viewable in compare view

Sourced from eventsource's releases.

v3.0.7

3.0.7 (2025-05-09)

Bug Fixes

• mark fetch init properties required in typings (1282872)

---

This release is also available on:

• npm package (@​latest dist-tag)

Sourced from eventsource's changelog.

3.0.7 (2025-05-09)

Bug Fixes

• mark fetch init properties required in typings (1282872)

• 270e7f2 chore(release): 3.0.7 [skip ci]
• 1282872 fix: mark fetch init properties required in typings
• See full diff in compare view

• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions