fix(deps): update dependency @whatwg-node/server to ^0.10.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@whatwg-node/server (source)	^0.9.60 -> ^0.10.0

---

Release Notes

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

v0.10.10

Compare Source

Patch Changes

• #​2452
  19c0be5
  Thanks @​ardatan! - Support AbortSignal.any on Node.js

• #​2452
  19c0be5
  Thanks @​ardatan! - Prevent custom AbortSignal to log
  "MaxListenersExceededWarning"

v0.10.9

Compare Source

Patch Changes

• #​2424
  28c4ad9
  Thanks @​ardatan! - Performance optimizations

  • Avoid creating AbortController and AbortSignal if not needed with new Request because it
    is expensive
  • Avoid creating a map for Headers and try to re-use the init object for Headers for
    performance with a single-line writeHead.
  • Avoid creating Buffer for string bodies for performance
  • Use setHeaders which accepts Headers since Node 18 if needed to forward Headers to Node

• 1642a76
  Thanks @​ardatan! - Remove unnecessary workaround for Bun

• Updated dependencies
  [28c4ad9]:

  • @​whatwg-node/fetch@​0.10.8

v0.10.8

Compare Source

Patch Changes

• 8eb332c
  Thanks @​ardatan! - Workaround for the bug in Node 24 and Deno don't
  like bound disposal functions

v0.10.7

Compare Source

Patch Changes

• #​2431
  085186b
  Thanks @​renovate! - Fix explicit resource management for Deno

v0.10.6

Compare Source

Patch Changes

• #​2383
  9527e8f
  Thanks @​ardatan! - Some implementations like compression npm
  package do not implement response.write(data, callback) signature, but whatwg-node/server waits
  for it to finish the response stream. Then it causes the response stream hangs when the
  compression package takes the stream over when the response data is larger than its threshold.

  It is actually a bug in compression package;
  expressjs/compression#46 But since it is a
  common mistake, we prefer to workaround this on our end.

  Now after calling response.write, it no longer uses callback but first it checks the result;

  if it is true, it means stream is drained and we can call response.end immediately. else if it
  is false, it means the stream is not drained yet, so we can wait for the drain event to call
  response.end.

• Updated dependencies
  [d86b4f3,
  9527e8f]:

  • @​whatwg-node/promise-helpers@​1.3.2
  • @​whatwg-node/fetch@​0.10.7

v0.10.5

Compare Source

Patch Changes

• b9f3629
  Thanks @​enisdenjo! - dependencies updates:
  • Updated dependency
    @whatwg-node/fetch@^0.10.6 ↗︎
    (from ^0.10.5, in dependencies)

v0.10.4

Compare Source

Patch Changes

• #​2305
  380984a
  Thanks @​enisdenjo! - Handle request abort signals with streamed
  body on uWS adapter

• #​2229
  9655941
  Thanks @​ardatan! - Simplify useContentEncoding plugin

• Updated dependencies
  [6bf6aa0]:

  • @​whatwg-node/promise-helpers@​1.3.1

v0.10.3

Compare Source

Patch Changes

• #​2208
  ff052a3
  Thanks @​ardatan! - When any Request method is called outside
  server adapter scope, it used to hang. This PR prevents it to hang and throw an error if the
  readable stream is destroyed earlier.

  let request: Request
  const adapter = createServerAdapter(req => {
    request = req
    return new Response('Hello World')
  })
  
  await request.text() // Was hanging but now throws an error

v0.10.2

Compare Source

Patch Changes

• ace1774
  Thanks @​ardatan! - Expose waitUntil method in the adapter

v0.10.1

Compare Source

Patch Changes

• #​2452
  19c0be5
  Thanks @​ardatan! - Support AbortSignal.any on Node.js

• #​2452
  19c0be5
  Thanks @​ardatan! - Prevent custom AbortSignal to log
  "MaxListenersExceededWarning"

v0.10.0

Compare Source

Minor Changes

• #​2068
  516bf60
  Thanks @​EmrysMyrddin! - Add new Instrumentation API

  Introduction of a new API allowing to instrument the graphql pipeline.

  This new API differs from already existing Hooks by not having access to input/output of phases.
  The goal of Instrumentation is to run allow running code before, after or around the whole
  process of a phase, including plugins hooks executions.

  The main use case of this new API is observability (monitoring, tracing, etc...).

Basic usage

import Sentry from '@​sentry/node'
import { createServerAdapter } from '@​whatwg-node/server'

const server = createServerAdapter(
  (req, res) => {
    //...
  },
  {
    plugins: [
      {
        instrumentation: {
          request: ({ request }, wrapped) =>
            Sentry.startSpan({ name: 'Graphql Operation' }, async () => {
              try {
                await wrapped()
              } catch (err) {
                Sentry.captureException(err)
              }
            })
        }
      }
    ]
  }
)

Multiple instrumentation plugins

It is possible to have multiple instrumentation plugins (Prometheus and Sentry for example), they
will be automatically composed by envelop in the same order than the plugin array (first is
outermost, last is inner most).

import { createServerAdapter } from '@​whatwg-node/server'

const server = createServerAdapter(
  (req, res) => {
    //...
  },
  { plugins: [useSentry(), useOpentelemetry()] }
)

sequenceDiagram
  Sentry->>Opentelemetry: ;
  Opentelemetry->>Server Adapter: ;
  Server Adapter->>Opentelemetry: ;
  Opentelemetry->>Sentry: ;

Loading

Custom instrumentation ordering

If the default composition ordering doesn't suite your need, you can manually compose
instrumentation. This allows to have a different execution order of hooks and instrumentation.

import { composeInstrumentation, createServerAdapter } from '@​whatwg-node/server'

const { instrumentation: sentryInstrumentation, ...sentryPlugin } = useSentry()
const { instrumentation: otelInstrumentation, ...otelPlugin } = useOpentelemetry()
const instrumentation = composeInstrumentation([otelInstrumentation, sentryInstrumentation])

const server = createServerAdapter(
  (req, res) => {
    //...
  },
  { plugins: [{ instrumentation }, sentryPlugin, otelPlugin] }
)

sequenceDiagram
  Opentelemetry->>Sentry: ;
  Sentry->>Server Adapter: ;
  Server Adapter->>Sentry: ;
  Sentry->>Opentelemetry: ;

Loading

Patch Changes

• #​2068
  516bf60
  Thanks @​EmrysMyrddin! - dependencies updates:
  • Updated dependency
    @whatwg-node/promise-helpers@^1.2.2 ↗︎
    (from ^1.0.0, in dependencies)
  • Added dependency
    @envelop/[email protected] ↗︎
    (to dependencies)
• Updated dependencies
  [516bf60]:
  • @​whatwg-node/promise-helpers@​1.2.3

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

[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.