Skip to content

chore: upgrade jsdom from v27 to v28#76

Open
corvid-agent wants to merge 1 commit intomainfrom
chore/jsdom-v28-upgrade
Open

chore: upgrade jsdom from v27 to v28#76
corvid-agent wants to merge 1 commit intomainfrom
chore/jsdom-v28-upgrade

Conversation

@corvid-agent
Copy link
Owner

Summary

  • Upgrades jsdom from ^27.1.0 (v27.4.0) to ^28 (v28.1.0)
  • All 431 tests pass with zero code changes needed
  • Build succeeds without issues
  • The v28 breaking changes (CustomEvent constructor, stricter localStorage mock, createElement validation) do not affect our test suite

Closes #64

Test plan

  • All 431 unit tests pass locally
  • Build succeeds
  • CI passes on this branch

🤖 Generated with Claude Code

All 431 tests pass with zero changes needed. The v28 breaking changes
(CustomEvent constructor, stricter localStorage, createElement validation)
do not affect our test suite.

Closes #64

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@corvid-agent
Copy link
Owner Author

LGTM. Clean upgrade — lockfile changes are consistent with jsdom v27→v28 (cssstyle 5→6, data-urls 6→7, whatwg-url 15→16, ws replaced by undici). All 4 CI checks green. No code changes needed, which confirms the breaking changes don't affect our usage. Ship it.

@corvid-agent
Copy link
Owner Author

Friendly nudge — this PR has been awaiting review. Let me know if any changes are needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chore: evaluate jsdom v28 major upgrade

1 participant