@whatwg-node/[email protected]

Patch Changes

• #2963
  99e6722
  Thanks @renovate! - Write string directly while sending
  request body to node:http's OutgoingMessage.

@whatwg-node/[email protected]

Patch Changes

• #2963
  99e6722
  Thanks @renovate! - Fix Node 24 + Express compatibility

• #2963
  99e6722
  Thanks @renovate! - Improve streaming

@whatwg-node/[email protected]

Patch Changes

• 0f53671
  Thanks @ardatan! - Add zstd to Accept-Encoding if available

@whatwg-node/[email protected]

Patch Changes

• 0f53671
  Thanks @ardatan! - Add zstd to Accept-Encoding if available

@whatwg-node/[email protected]

Patch Changes

• #2910
  0079afd
  Thanks @ardatan! - Zstandard `zstd` support

• Updated dependencies
  [0079afd]:

  • @whatwg-node/[email protected]

@whatwg-node/[email protected]

Patch Changes

• #2910
  0079afd
  Thanks @ardatan! - Zstandard `zstd` support

@whatwg-node/[email protected]

Patch Changes

• #2910
  0079afd
  Thanks @ardatan! - Zstandard `zstd` support

• Updated dependencies
  [0079afd]:

  • @whatwg-node/[email protected]

@whatwg-node/[email protected]

Patch Changes

• c9b2c87
  Thanks @ardatan! - Do not override existing `user-agent`

• Updated dependencies
  [c9b2c87]:

  • @whatwg-node/[email protected]

@whatwg-node/[email protected]

Patch Changes

• c9b2c87
  Thanks @ardatan! - Do not override existing `user-agent`

@whatwg-node/[email protected]

Patch Changes

• c9b2c87
  Thanks @ardatan! - Do not override existing `user-agent`

• Updated dependencies
  [c9b2c87]:

  • @whatwg-node/[email protected]

@whatwg-node/[email protected]

Patch Changes

• 2fa56ae
  Thanks @ardatan! - Fix the incompatibility issue between Bun.serve
  and the adapter

@whatwg-node/[email protected]

Patch Changes

• #2821
  93f2932
  Thanks @ardatan! - Fix handling multiple set-cookie headers
  correctly with uWebSockets.js integration

@whatwg-node/[email protected]

Patch Changes

• #2821
  93f2932
  Thanks @ardatan! - Fix handling multiple set-cookie headers
  correctly with uWebSockets.js integration

@whatwg-node/[email protected]

Patch Changes

• Updated dependencies
  [60d41d6]:
  • @whatwg-node/[email protected]

@whatwg-node/[email protected]

Minor Changes

• #2786
  60d41d6
  Thanks @ardatan! - Add User-Agent with node value by default
  similar to undici, because fetch implementation should provide one if the user doesn't provide
  one per WHATWG spec

@whatwg-node/[email protected]

Patch Changes

• #2656
  d2ef55c
  Thanks @renovate! - Fix TypeScript issues and bump the version
  to get performance improvements for all dependent packages
• Updated dependencies
  [d2ef55c]:
  • @whatwg-node/[email protected]

@whatwg-node/[email protected]

Patch Changes

• #2656
  d2ef55c
  Thanks @renovate! - Fix TypeScript issues and bump the version
  to get performance improvements for all dependent packages

@whatwg-node/[email protected]

Patch Changes

• #2656
  d2ef55c
  Thanks @renovate! - Fix TypeScript issues and bump the version
  to get performance improvements for all dependent packages
• Updated dependencies
  [d2ef55c]:
  • @whatwg-node/[email protected]

@whatwg-node/[email protected]

Patch Changes

• #2643
  941e5ce
  Thanks @ardatan! - In case of iterator cancellation, ensure the
  response stream a.k.a. IncomingMessage is properly closed.

  const response = await fetch('http://localhost:3000/stream')
  
  for await (const chunk of response.body) {
    console.log('Received chunk:', chunk)
    if (chunk === 'stop') {
      console.log('Stopping stream')
      // In case of `break` which calls the `iterator.return()`, we need to ensure the stream is closed properly.
      break
    }
  }

@whatwg-node/[email protected]

Patch Changes

• #2632
  7a44c69
  Thanks @ardatan! - Avoid Node's promise pipeline by piping streams
  directly

@whatwg-node/[email protected]

Patch Changes

• #2640
  22c568e
  Thanks @ardatan! - Handle string bodies without streams to fix the
  performance regression