chore(deps): upgrade vitest 3 → 4 and jsdom 26 → 29#29
Merged
craigmorrison merged 1 commit intomainfrom Apr 17, 2026
Merged
Conversation
No existing tests so this is purely a version bump; vitest 4.1.4 boots cleanly with the same vitest.config.ts and jsdom 29 is a drop-in replacement.
craigmorrison
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Major version bumps for the two testing deps flagged in the upgrade review.
vitest:^3.0.0→^4.0.0jsdom:^26.0.0→^29.0.0No existing tests in the repo (
packages/*/src/**/*.{test,spec}.{ts,tsx,js,jsx}is empty), so this is a clean version bump. Verified locally:npm run test→ vitest 4.1.4 loads the config and exits 0 (no tests)npm run lint→ no new issues (pre-existing warning in app-people-list only)npm run build→portal-shell-ssrbuild failure is pre-existing on main, unrelated to this changeNote: the branch commit message contains literal
\u2192escapes — the squash-merge commit will use this (corrected) PR title instead.