December 17, 2024

@whatwg-node/server@0.9.64

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/server@0.9.63

Patch Changes

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

December 12, 2024

@whatwg-node/server@0.9.62

Patch Changes

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

December 10, 2024

@whatwg-node/node-fetch@0.7.5

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/server@0.9.61

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/server@0.9.60

Patch Changes

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

November 25, 2024

@whatwg-node/server@0.9.59

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/server@0.9.58

Patch Changes

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

November 25, 2024

@whatwg-node/node-fetch@0.7.4

Patch Changes

• e88ab4a
  Thanks @ardatan! - dependencies updates:
  • Added dependency
    @whatwg-node/disposablestack@^0.0.5 ↗︎
    (to dependencies)

@whatwg-node/server@0.9.57

Patch Changes

• e88ab4a
  Thanks @ardatan! - dependencies updates:

  • Added dependency
    @whatwg-node/disposablestack@^0.0.5 ↗︎
    (to dependencies)

• e88ab4a
  Thanks @ardatan! - New Explicit Resource Management feature for the
  server adapters;
  Learn more

  • Symbol.dispose and Symbol.asyncDispose hooks When the server adapter plugin has these hooks,
    it is added to the disposable stack of the server adapter. When the server adapter is disposed,
    those hooks are triggered
  • disposableStack in the server adapter The shared disposable stack that will be triggered when
    Symbol.asyncDispose is called.
  • Automatic disposal on Node and Node-compatible environments Even if the server adapter is not
    disposed explicitly, the disposal logic will be triggered on the process termination (SIGINT,
    SIGTERM etc)
  • ctx.waitUntil relation If it is an environment does not natively provide waitUntil, the
    unresolved passed promises will be resolved by the disposable stack.

November 19, 2024

@whatwg-node/node-fetch@0.7.3

Patch Changes

• #1814
  54c244d
  Thanks @ardatan! - Small improvements for Bun support

@whatwg-node/server@0.9.56

Patch Changes

• #1814
  54c244d
  Thanks @ardatan! - Small improvements for Bun support

November 14, 2024

@whatwg-node/server@0.9.55

Patch Changes

• #1799
  7d1f0ff
  Thanks @ardatan! - Avoid polluting the original object in case of
  `Object.create`