chore(deps): upgrade vitest to 4.1.11 and refresh dompurify - #105
Merged
Merged
Conversation
Fixes the open security alerts for vitest/@vitest/mocker (path traversal, fixed in 4.1.11) and dompurify (fixed in 3.4.13, pulled in by jspdf). vitest 4.1.11 still accepts @types/node ^20, unlike vitest 5.
npm 11 dropped the optional @emnapi packages that npm 10 (Node 22, used in CI) expects, so npm ci failed.
This was referenced Oct 1, 2026
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.
Fixes the last open security alerts on toolbelt:
@types/node22+ and we're on 20. 4.1.11 is the smallest version with the fix and still accepts^20.The undici alerts were fixed by #79.
The other lockfile changes are all inside vitest's own tree. No app code changes. Locally: 56 tests pass on vitest 4, lint has 0 errors, and the build succeeds.