fix(deps): update dependency @whatwg-node/server to v0.9.65

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@whatwg-node/server (source)	0.9.49 -> 0.9.65

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

ardatan/whatwg-node (@​whatwg-node/server)

v0.9.65

Compare Source

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

v0.9.64

Compare Source

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'

v0.9.63

Compare Source

Patch Changes

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

v0.9.62

Compare Source

Patch Changes

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

v0.9.61

Compare Source

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)

v0.9.60

Compare Source

Patch Changes

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

v0.9.59

Compare Source

Patch Changes

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

v0.9.58

Compare Source

Patch Changes

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

v0.9.57

Compare Source

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.

v0.9.56

Compare Source

Patch Changes

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

v0.9.55

Compare Source

Patch Changes

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

v0.9.54

Compare Source

Patch Changes

• #​1790
  c7d49b1
  Thanks @​ardatan! - Handle request abort correctly with AbortSignal

v0.9.53

Compare Source

Patch Changes

• Updated dependencies
  [6c006e1]:
  • @​whatwg-node/fetch@​0.10.0

v0.9.52

Compare Source

Patch Changes

• 323a519
  Thanks @​ardatan! - Allow other libs to redefine Request's
  properties

v0.9.51

Compare Source

Patch Changes

• #​1644
  637185f
  Thanks @​renovate! - Respect given fetchAPI

• Updated dependencies []:

  • @​whatwg-node/fetch@​0.9.23

v0.9.50

Compare Source

Patch Changes

• 9281e02
  Thanks @​ardatan! - Improvements with uWS Body handling

• Updated dependencies
  [77dd1c3]:

  • @​whatwg-node/fetch@​0.9.22

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[Tobbe]

I had to update how we're calling normalizeNodeRequest(). I'm basing my change on how whatwg-node updated the code in this commit ardatan/whatwg-node@637185f

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.