chore: upgrade jsdom to latest (v26.0.0)

[jeremy-daley-kr]

Summary

The initial motivation for this was simply to get rid of a deprecation notice from Node v22 about punycode:

punycode
  <- psl
    <- tough-cookie (replaces psl in v5.0.0)
      <- jsdom (upgrade gets that ^ replacement)

...But ultimately, we're talking about a 4-majors-behind package... so hopefully nothing blows up.

Test plan

[linux-foundation-easycla]

• ❌ - login: @jeremy-daley-kr / name: Jeremy Daley . The commit (39a18e9) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[netlify]

✅ Deploy Preview for jestjs ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	39a18e9
🔍 Latest deploy log	https://app.netlify.com/sites/jestjs/deploys/679926b72c3bd10008d51845
😎 Deploy Preview	https://deploy-preview-15481--jestjs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Smrtnyk]

duplicate of #15473

[jeremy-daley-kr]

duplicate of #15473

Oh! Nice... I'll look into the e2e snapshots thing he mentioned

[Smrtnyk]

duplicate of #15473

Oh! Nice... I'll look into the e2e snapshots thing he mentioned

keep in mind that even that PR might not get accepted
#15417
due to node versions that jest supports

just something to consider before you invest more time

[jeremy-daley-kr]

duplicate of #15473

Oh! Nice... I'll look into the e2e snapshots thing he mentioned

keep in mind that even that PR might not get accepted #15417 due to node versions that jest supports

just something to consider before you invest more time

Hmm. Is this a touchy subject? I'm trying to understand the attachment to a Node version (16) that's already reached end of life.

[Smrtnyk]

duplicate of #15473

Oh! Nice... I'll look into the e2e snapshots thing he mentioned

keep in mind that even that PR might not get accepted #15417 due to node versions that jest supports
just something to consider before you invest more time

Hmm. Is this a touchy subject? I'm trying to understand the attachment to a Node version (16) that's already reached end of life.

From what I understand jsdom update requires jest to drop support for node 16 which seems like maintainer still want to support, so various previous community driven attempts to update jsdom were rejected.
Let's see, maybe something changes in that regard

[BernhardBehrendt]

I'm affected by an issue regarding CSS parsing which is related to the old jsdom version. So it would be beneficial to get this lib updated as it's actually causing tons of those errors in my unit tests.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.