@whatwg-node/promise-helpers
2.0.2 · 10 Nov 2026MIT34.4M / weekRepositoryHomepagenpmAtom feed
Upgrading @whatwg-node/promise-helpers From 1.2.1 to 2.0.2
10 releases in betweenevery note read
Reading releases, release notes and advisories…
- 3
- changes to make
- 0
- advisories fixed
- 1
- new
- 7
- fixes
Before you upgrade
Tick each one off as you go- Breaking2.0.0
- Breaking2.0.0
- Breaking1.2.2
Release by release
- Fixed
Use shared prototype classes for
fakePromise/fakeRejectPromiseinstances.
- Fixed
- Fixed
Make
handleMaybePromiseavoid temporary fake-promise wrappers on the synchronous path.
- Fixed
- Breaking
Drop support for Node.js 18 and 20. The minimum supported Node.js version is now 22.15.
- Breaking
Remove deprecated
mapMaybePromisein favor ofhandleMaybePromise.
- Breaking
- Fixed
Reuse fake promise Symbol
- Fixed
- Fixed
Fix types by replacing
VoidFunctiontype to() => void
- Fixed
- New
Allow to pass a finally callback to
handleMaybePromise
- New
- Fixed
Name functions in
iterateAsyncfor more readable traces
- Fixed
- Fixed
Do not consider fake promises as real promises
- Fixed
8 other lines we could not sort, mostly version bumps
- 2.0.0
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.0consumers. - 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. NativeCustomEvent/Event/EventTargetare available on Node.js 22+, so the ponyfill is no longer maintained; use the platform globals. - 2.0.0
@whatwg-node/fetch: dropped therequire("crypto").webcryptofallback;cryptois alwaysglobalThis.cryptoon supported runtimes. - 2.0.0
@whatwg-node/server: removed the Node 18setHeadersworkaround (isNode1x);ServerResponse#setHeadersis used whenever it exists. - 2.0.0
@whatwg-node/node-fetch: Runtime guards forzlib.createZstdCompress/createZstdDecompressare removed;zstdis always included inAccept-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.
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.