July 24, 2024

@whatwg-node/[email protected]

Patch Changes

• #1481
  481bdfd
  Thanks @ardatan! - Send supported encoding formats in
  `accept-encoding` header by default

@whatwg-node/[email protected]

Patch Changes

• #1481
  481bdfd
  Thanks @ardatan! - New plugin to handle E2E request compression

  When the client provides Accept-Encoding header, if the server supports the encoding, it will
  compress the response body. This will reduce the size of the response body and improve the
  performance of the application.

  On the other hand, if the client sends Content-Encoding header, the server will decompress the
  request body before processing it. This will allow the server to handle the request body in its
  original form. If the server does not support the encoding, it will respond with
  415 Unsupported Media Type status code.

  serverAdapter's fetch function handles the compression and decompression of the request and
  response bodies.

  import { createServerAdapter, Response, useContentEncoding } from '@whatwg-node/server'
  
  const serverAdapter = createServerAdapter(() => Response.json({ hello: 'world' }), {
    plugins: [useContentEncoding()]
  })

July 23, 2024

[email protected]

Patch Changes

• 145e46e
  Thanks @ardatan! - Implement .bytes method for Blob and Body,
  now Uint8Array is available with bytes format

@whatwg-node/[email protected]

Patch Changes

• 145e46e
  Thanks @ardatan! - Implement .bytes method for Blob and Body,
  now Uint8Array is available with bytes format

July 20, 2024

@whatwg-node/[email protected]

Patch Changes

• 1c5b838
  Thanks @ardatan! - Fix Request.clone and Response.clone

June 24, 2024

@whatwg-node/[email protected]

Patch Changes

• #1407
  ebbc85b
  Thanks @Akryum! - Vary: Access-Control-Request-Headers would
  overwrite Vary: Origin

June 21, 2024

@whatwg-node/[email protected]

Patch Changes

• cf07839
  Thanks @ardatan! - Fixes TypeScript v5.5 compatibility issues

June 01, 2024

@whatwg-node/[email protected]

Patch Changes

• #1328
  36904b4
  Thanks @ardatan! - Add skipPonyfill flag to createFetch to skip
  ponyfills and use the native Fetch implementation for Node.js

April 26, 2024

@whatwg-node/[email protected]

Patch Changes

• e6234df Thanks @ardatan! - Handle request errors properly

@whatwg-node/[email protected]

Patch Changes

• e6234df Thanks @ardatan! - Do not call res.onAborted multiple times because it causes it to overwrite the previous listener, and use AbortSignal's abort event instead

April 15, 2024

@whatwg-node/[email protected]

Patch Changes

• #1246 4717be5 Thanks @ardatan! - Ensure unique context objects are sent per each request.

  For example in CloudFlare Workers,
  fetch receives env and ctx, and env is shared across requests. That causes the server receives the same context object for each request.
  Now the server creates a new context object for each request, even if the first argument is the same. Before, it always takes the first argument as the context object, then merges the following arguments into it.

March 25, 2024

@whatwg-node/[email protected]

Patch Changes

• #1224 d6bec0a Thanks @ardatan! - Introduce handleRequestFromResponse method for a better Fastify integration

March 22, 2024

@whatwg-node/[email protected]

Patch Changes

• #1219 fa097a4 Thanks @ardatan! - Support blob: object URLs

• #1219 fa097a4 Thanks @ardatan! - Throw TypeError when multipart request is unable to parse as FormData

• #1220 ac6b719 Thanks @ardatan! - Do not throw when Curl request cancellation

@whatwg-node/[email protected]

Patch Changes

• #1220 ac6b719 Thanks @ardatan! - Fix UWS's behavior in case of request cancellation

• #1220 ac6b719 Thanks @ardatan! - Use ServerResponse's close event to catch request cancellation