Packages

@whatwg-node/cookie-store

0.3.0 · 21 Sep 2026MIT185.7k / weekRepositoryHomepagenpmAtom feed

Upgrading @whatwg-node/cookie-store From 0.2.2 to 0.3.0

2 releases in betweenevery note read

Reading releases, release notes and advisories…

  1. 0.2.2yours
  2. 0.2.3
  3. 0.3.0target
  4. 154 pre
1
change to make
0
advisories fixed
0
new
0
fixes

Before you upgrade

Tick each one off as you go
  • Breaking0.3.0
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).

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

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

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

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

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

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

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

    0.3.0

3 internal lines (docs, tests, tooling) left out.

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.