Packages

@happy-dom/jest-environment

21.0.4 · 20 Oct 2026MIT269.4k / weekRepositoryHomepagenpmAtom feed

Upgrading @happy-dom/jest-environment From 10.5.3 to 21.0.4

372 releases in betweennotes for 344

Reading releases, release notes and advisories…

Other targets from 10.5.3Newest 10.x10.11.2
  1. 10.5.3yours
  2. 16 releases
  3. 11.0.0major
  4. 10 releases
  5. 12.0.0major
  6. 27 releases
  7. 13.0.0security
  8. 52 releases
  9. 14.0.0major
  10. 43 releases
  11. 15.0.0major
  12. 26 releases
  13. 15.10.2security
  14. 14 releases
  15. 16.0.0major
  16. 28 releases
  17. 17.0.0major
  18. 50 releases
  19. 18.0.0major
  20. 1 release
  21. 19.0.0major
  22. 2 releases
  23. 20.0.0security
  24. 20.0.1security
  25. 47 releases
  26. 20.8.8security
  27. 20.8.9security
  28. 36 releases
  29. 20.14.6security
  30. 21.0.0security
  31. 1 release
  32. 21.0.2security
  33. 21.0.3security
  34. 21.0.4target
14+
changes to make
0
advisories fixed
151+
new
250+
fixes

Counted from 344 of 372 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking20.0.0
  • Breaking20.0.0
  • Breaking19.0.0
  • Breaking18.0.0
  • Breaking17.0.0
  • Breaking16.0.0
  • Breaking15.0.0
  • Breaking14.0.0
  • Breaking13.0.0
  • Breaking12.0.0

Security

  • Fixed a code injection vulnerability in the ESM compiler - By @capricorn86

    21.0.4
  • Fixes security vulnerability where authorization header was forwarded when redirecting - By @capricorn86

    21.0.3
  • Fixes SSRF security vulnerability by doing a target-origin bypass in the proxy server in @happy-dom/server-renderer - By @capricorn86

    21.0.2
  • Disables CSS and IFrame loading by default to prevent server-side request forgery (SSRF) - By @capricorn86

    21.0.0
  • Fixes cookie scope forgery vulnerability - By @capricorn86

    20.14.6
  • A security advisory (GHSA-w4gp-fjgq-3q4g) was reported for this security vulnerability.

    20.8.9
  • A security advisory (GHSA-6q6h-j7hj-3r64) has been reported that shows a security vulnerability where it may be possible to escape the VM context and get access to process level functionality in unsafe environments using CommonJS.

    20.8.8
  • A security advisory has been reported showing that the recommended preventive measure of running Node.js with --disallow-code-generation-from-strings wasn't enough to protect against attackers escaping the VM context and accessing process-level functions.

    20.0.1
  • A security advisory (GHSA-37j7-fg3j-429f) has been reported that shows a security vulnerability where it's possible to escape the VM context and get access to process level functionality.

    20.0.0
  • Fixes a security vulnerability that allowed for server side code to be executed by a <script> tag - By @capricorn86 in task #1585

    15.10.2

Release by release

  1. 21.0.4

    Security fix20 Oct 20261 fix
    • Security

      Fixed a code injection vulnerability in the ESM compiler - By @capricorn86

    • Fixed

      Fixed cross-origin isolation so opaque-origin data: iframes cannot access their parent or top window - By @capricorn86

  2. 21.0.3

    Security fix15 Oct 2026
    • Security

      Fixes security vulnerability where authorization header was forwarded when redirecting - By @capricorn86

  3. 21.0.2

    Security fix15 Oct 2026
    • Security

      Fixes SSRF security vulnerability by doing a target-origin bypass in the proxy server in @happy-dom/server-renderer - By @capricorn86

  4. 21.0.1

    12 Oct 20261 new
  5. 21.0.0

    Security fix11 Oct 2026
  6. 20.14.6

    Security fix8 Oct 2026
    • Security

      Fixes cookie scope forgery vulnerability - By @capricorn86

  7. 20.14.5

    12 Sep 20261 fix
    • Fixed

      Preserve character references in comment data - By @hampustagerud in task #2409

  8. 20.14.4

    12 Sep 20261 fix
    • Fixed

      End comments at the first comment end tag when it overlaps a comment start tag - By @hampustagerud in task #2407

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