build(deps-dev): Bump jsdom and @types/jsdom (#2965)

[KATO-Hiro]

close #2965

Summary by CodeRabbit

• Chores

  • Updated development dependencies, including jsdom and related type definitions, to latest versions with performance improvements, bug fixes, and enhanced spec conformance.

• Documentation

  • Added comprehensive upgrade documentation detailing breaking changes, new features, CSS and event API improvements, verification checklist, testing procedures, and implementation results for the dependency update.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This pull request upgrades jsdom and @types/jsdom to major versions (v27.x), with comprehensive documentation of breaking changes, new features, verification procedures, and upgrade outcomes included in a new development notes file.

Changes

Cohort / File(s)	Summary
Dependency Upgrade package.json	Updated jsdom from 26.1.0 to 27.3.0 and @types/jsdom from 21.1.7 to 27.0.0
Upgrade Documentation docs/dev-notes/2025-12-17/bump-jsdom-from-v26.x-to-v27.x/plan.md	New document detailing upgrade plan, including breaking changes (virtual console, event API, CSS engine, UA stylesheet, input pattern, Node.js version), new features, verification checklist, implementation notes, and results

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Notable areas for attention:
  • Verify the documented breaking changes are accurate and complete for v27.x
  • Confirm verification checklist outcomes align with actual test runs
  • Ensure all related codebase changes beyond package.json dependencies are accounted for

Poem

🐰 A major leap, from version old to new,
jsdom's been bumped from twenty-six to twenty-seven true!
The docs lay plain each change and test,
This upgrade plan puts quality to the test. ✨

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: bumping jsdom and @types/jsdom dependencies, which matches the changeset modifications in package.json.
Linked Issues check	✅ Passed	The pull request closes issue #2965 which has the same title and objective as this PR, indicating alignment with the linked issue requirements.
Out of Scope Changes check	✅ Passed	All changes are directly related to the dependency upgrade objective: package.json updates and supporting documentation in dev-notes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch #2965

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between fd4ed17 and 1abedcf.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• docs/dev-notes/2025-12-17/bump-jsdom-from-v26.x-to-v27.x/plan.md (1 hunks)
• package.json (2 hunks)

🔇 Additional comments (7)

docs/dev-notes/2025-12-17/bump-jsdom-from-v26.x-to-v27.x/plan.md (5)

1-17: Well-structured documentation.

The document header and table of contents provide clear context and navigation. The metadata (creation date, target versions, status, priority) is helpful for tracking the upgrade process.

---

113-179: Excellent documentation of new features.

The new features section provides clear examples of newly available APIs and improvements. The CSS selector engine improvements (20+ bug fixes) are particularly valuable for test accuracy.

---

181-235: Thorough verification and excellent lessons learned.

The verification results demonstrate comprehensive testing (1745 tests passed) and the lessons learned section provides valuable insights for future upgrades. The documentation of actual results with timestamps adds credibility to the upgrade process.

---

238-243: Good references provided.

The references section includes appropriate links to official jsdom documentation and release notes, which are essential for understanding the upgrade details.

---

20-111: jsdom v27 Breaking Changes: Impact Assessment Accurate

All six breaking changes are properly documented with correct impact assessments:

1. ✅ Virtual Console API — sendTo() → forwardTo() and omitJSDOMErrors → jsdomErrors: No impact (codebase shows zero virtualConsole usage)

2. ✅ Event API — Click event changes: No impact (unit tests contain no direct .click() calls; only Playwright E2E tests use clicks via real browser, which is jsdom-independent)

3. ✅ CSS Selector Engine — nwsapi → @asamuzakjp/dom-selector: Improvement with 20+ bug fixes (querySelector usage is not complex in this project)

4. ✅ User Agent Stylesheet — Chromium-derived → HTML Standard-derived: No impact (getComputedStyle searches return zero results)

5. ✅ Input pattern Attribute Flag — u → v regex flag: No impact (no pattern="" attributes found in codebase)

6. ✅ Node.js Minimum Version — v18.0.0 → v20.0.0+: No impact (environment runs Node.js 22; engines.node already configured)

The documentation thoroughness and impact analysis are solid. All feature non-usage claims are code-verified.

package.json (2)

53-53: jsdom v27.3.0 is available and secure.

jsdom v27.3.0 was published 8 days ago and no direct vulnerabilities have been found for this package in Snyk's vulnerability database. The upgrade is safe to proceed with.

---

43-43: No action required. @types/jsdom@27.0.0 correctly provides type definitions for jsdom v27.3.0, with no compatibility issues.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[KATO-Hiro]

LGTM