Packages

@whatwg-node/promise-helpers

2.0.2 · 10 Nov 2026MIT34.4M / weekRepositoryHomepagenpmAtom feed

Upgrading @whatwg-node/promise-helpers From 1.3.0 to 2.0.2

5 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 1.3.0Newest 1.x1.3.2
  1. 1.3.0yours
  2. 1.3.1
  3. 1.3.2
  4. 2.0.0major
  5. 2.0.1
  6. 2.0.2target
  7. 168 pre
2
changes to make
0
advisories fixed
0
new
4
fixes

Before you upgrade

Tick each one off as you go
  • Breaking2.0.0
  • Breaking2.0.0

Release by release

  1. 2.0.2

    10 Nov 20261 fix
    • Fixed

      Use shared prototype classes for fakePromise / fakeRejectPromise instances.

  2. 2.0.1

    26 Oct 20261 fix
    • Fixed

      Make handleMaybePromise avoid temporary fake-promise wrappers on the synchronous path.

  3. 2.0.0

    Migration needed21 Sep 2026
    • Breaking

      Drop support for Node.js 18 and 20. The minimum supported Node.js version is now 22.15.

    • Breaking

      Remove deprecated mapMaybePromise in favor of handleMaybePromise.

  4. 1.3.2

    10 May 20251 fix
    • Fixed

      Reuse fake promise Symbol

  5. 1.3.1

    14 Apr 20251 fix
    • Fixed

      Fix types by replacing VoidFunction type to () => void

8 other lines we could not sort, mostly version bumps
  • 0.x packages: minor bump (breaking changes are allowed in minors while major is 0).

    2.0.0
  • 1.x packages (@whatwg-node/promise-helpers, @whatwg-node/server-plugin-cookies): major bump, since dropping supported Node versions is a breaking engines change for SemVer >=1.0.0 consumers.

    2.0.0
  • engines.node: all published packages now declare >=22.15.0 (including @whatwg-node/promise-helpers, which was still on >=16).

    2.0.0
  • @whatwg-node/events: removed. Native CustomEvent / Event / EventTarget are available on Node.js 22+, so the ponyfill is no longer maintained; use the platform globals.

    2.0.0
  • @whatwg-node/fetch: dropped the require("crypto").webcrypto fallback; crypto is always globalThis.crypto on supported runtimes.

    2.0.0
  • @whatwg-node/server: removed the Node 18 setHeaders workaround (isNode1x); ServerResponse#setHeaders is used whenever it exists.

    2.0.0
  • @whatwg-node/node-fetch: Runtime guards for zlib.createZstdCompress / createZstdDecompress are removed; zstd is always included in Accept-Encoding.

    2.0.0
  • CI / e2e: unit matrix is [22, 24, 26]; AWS Lambda runtime and Azure Function target moved from Node 20 to Node 22.

    2.0.0

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.