Upgrading jsdom 26 to 27
Breaking26.1.0 → 27.4.0Breaking4New6Changed11Fixed19
BreakingUpgrade verdict
4 breaking changes.
In plain terms
- Breaking change: upgraded tough-cookie, which now considers URLs like http://localhost/ to be secure contexts (per the spec), and thus will return Secure-flagged cookies for such URLs.
- Significantly improved specification conformance for the Window object, including named properties and changing various data properties to accessor properties.
- The user agent stylesheet is now derived from the HTML Standard, instead of from Chromium.
- The virtual console has seen a number of changes.
Must act Top 3 of 4 that need code or config changes
Node.js requirement changed in 27.1.0: >=18 → ^20.19.0 || ^22.12.0 || >=24.0.0.
Adds @acemir/cssom ^0.9.28, @asamuzakjp/dom-selector ^6.7.6, @exodus/bytes ^1.6.0.
Drops nwsapi, rrweb-cssom, whatwg-encoding.
Installs 44 packages in all (was 38).
What you must change
Breaking4
Breaking change: upgraded tough-cookie, which now considers URLs like http://localhost/ to be secure contexts (per the spec), and thus will return Secure-flagged cookies for such URLs.
tough-cookiehttp://localhost/SecureSignificantly improved specification conformance for the Window object, including named properties and changing various data properties to accessor properties.
WindowThe user agent stylesheet is now derived from the HTML Standard, instead of from Chromium.
getComputedStyle()The virtual console has seen a number of changes.
"jsdomError"typesendTo()forwardTo()jsdomErrorsomitJSDOMErrors