January 10, 2025

@whatwg-node/[email protected]

Patch Changes

• #1961
  2785c80
  Thanks @ardatan! - ReadableStream's Symbol.asyncIterator now
  returns AsyncIterableIterator like before even if it is ok to return AsyncIterator right now.
  It is safer to return AsyncIterableIterator because it is a common mistake to use
  AsyncIterator as AsyncIterable.
• Updated dependencies
  [2785c80]:
  • @whatwg-node/[email protected]

@whatwg-node/[email protected]

Patch Changes

• #1961
  2785c80
  Thanks @ardatan! - ReadableStream's Symbol.asyncIterator now
  returns AsyncIterableIterator like before even if it is ok to return AsyncIterator right now.
  It is safer to return AsyncIterableIterator because it is a common mistake to use
  AsyncIterator as AsyncIterable.

January 10, 2025

@whatwg-node/[email protected]

Patch Changes

• #1929
  b88b85c
  Thanks @ardatan! - dependencies updates:
  • Updated dependency
    @whatwg-node/node-fetch@^0.7.5 ↗︎
    (from ^0.7.1, in dependencies)
• Updated dependencies
  [b88b85c,
  9b39c3e,
  b88b85c]:
  • @whatwg-node/[email protected]

@whatwg-node/[email protected]

Patch Changes

• #1929
  b88b85c
  Thanks @ardatan! - dependencies updates:

  • Removed dependency
    @kamilkisiela/fast-url-parser@^1.1.4 ↗︎
    (from dependencies)
  • Removed dependency
    fast-querystring@^1.1.1 ↗︎ (from
    dependencies)

• #1947
  9b39c3e
  Thanks @ardatan! - Remove the event listener on the provided
  AbortSignal when node-libcurl is used, the connection finishes to prevent potential memory
  leaks;

  const res = await fetch(URL, { signal: new AbortController().signal })
  // AbortController is never aborted, and HTTP request is done as expected successfully

• #1929
  b88b85c
  Thanks @ardatan! - - Remove URL ponyfill implementation based on
  fast-url-parser and fast-querystring, because Node now uses Ada URL parser which is fast
  enough.

  • Fix ReadableStream[Symbol.asyncIterator]

  ReadableStream uses Readable so it uses Symbol.asyncIterator method of Readable but the
  returned iterator's .return method doesn't handle cancellation correctly. So we need to call
  readable.destroy(optionalError) manually to cancel the stream.

  This allows ReadableStream to use implementations relying on AsyncIterable.cancel to handle
  cancellation like Readable.from

  Previously the following was not handling cancellation;

  const res = new ReadableStream({
    start(controller) {
      controller.enqueue('Hello')
      controller.enqueue('World')
    },
    cancel(reason) {
      console.log('cancelled', reason)
    }
  })
  
  const readable = Readable.from(res)
  
  readable.destroy(new Error('MY REASON'))
  
  // Should log 'cancelled MY REASON'

December 24, 2024

@whatwg-node/[email protected]

Patch Changes

• #1926
  bae5de1
  Thanks @ardatan! - While calling handleNodeRequest or
  handleNodeRequestAndResponse, waitUntil is not added automatically as in requestListener for
  Node.js integration. This change adds waitUntil into the serverContext if not present.

  Fixes the issue with Fastify integration that uses the mentioned methods

December 17, 2024

@whatwg-node/[email protected]

Patch Changes

• #1899
  a84e84a
  Thanks @ardatan! - - New onDispose hook which is alias of
  Symbol.asyncDispose for Explicit Resource Management

  • Registration of the server adapter's disposal to the global process termination listener is now
    opt-in and configurable.

  const plugin: ServerAdapterPlugin = {
    onDispose() {
      console.log('Server adapter is disposed')
    }
  }
  
  const serverAdapter = createServerAdapter(() => new Response('Hello world!'), {
    plugins: [plugin],
    // Register the server adapter's disposal to the global process termination listener
    // Then the server adapter will be disposed when the process exit signals only in Node.js!
    disposeOnProcessTerminate: true
  })
  
  await serverAdapter.dispose()
  // Prints 'Server adapter is disposed'

December 13, 2024

@whatwg-node/[email protected]

Patch Changes

• c75e6e3
  Thanks @ardatan! - Export `DisposableSymbols` for disposable
  plugins

December 12, 2024

@whatwg-node/[email protected]

Patch Changes

• #1880
  95e5ce4
  Thanks @EmrysMyrddin! - Docs for hooks

December 10, 2024

@whatwg-node/[email protected]

Patch Changes

• #1872
  7fb47d8
  Thanks @ardatan! - Fix the error thrown `ENOTFOUND` when a parsed
  URL with IPV6 hostname is given

  Instead of using the parsed URL passed to the fetch function, let node:http parse it again.
  This way, the IPV6 hostname is correctly resolved.

• #1872
  7fb47d8
  Thanks @ardatan! - url.searchParams parameter should reflect the
  changes in toString()

  const url = new URL('http://example.com/?a=b')
  url.searchParams.set('a', 'c')
  console.log(url.toString()) // http://example.com/?a=c

• #1872
  7fb47d8
  Thanks @ardatan! - Fix IPV6 parsing in `URL`;

  new URL('http://[::1]') should parse the host as `[::1]` not `::1`.

@whatwg-node/[email protected]

Patch Changes

• #1872
  7fb47d8
  Thanks @ardatan! - Wait for remaining promises during asyncDispose
  correctly

  The asyncDispose function should wait for all remaining promises to resolve before returning.
  This ensures that the server is fully disposed of before the function returns.

  import { createServerAdapter } from '@whatwg-node/server'
  
  const deferred = Promise.withResolvers()
  
  const adapter = createServerAdapter((req, ctx) => {
    ctx.waitUntil(deferred.promise)
    return new Response('Hello, world!')
  })
  
  const res = await adapter.fetch('http://example.com')
  console.assert(res.status === 200)
  console.assert((await res.text()) === 'Hello, world!')
  
  let disposed = false
  adapter[Symbol.asyncDispose]().then(() => {
    disposed = true
  })
  
  console.assert(!disposed)
  
  deferred.resolve()
  
  console.assert(disposed)

November 25, 2024

@whatwg-node/[email protected]

Patch Changes

• #1838
  8947888
  Thanks @ardatan! - Respect SIGTERM as termination event

November 25, 2024

@whatwg-node/[email protected]

Patch Changes

• b4ab548
  Thanks @ardatan! - Remove SIGTERM from termination events to prevent
  hangs, and always add disposable stack to the termination events

November 25, 2024

@whatwg-node/[email protected]

Patch Changes

• 5a9098c
  Thanks @ardatan! - Fix on plugin types