[npm audit fix] update vite, etc. - #16
Merged
Merged
Conversation
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.
Note
Low Risk
Lockfile-only dependency bumps (including
vite) with no source changes; risk is limited to potential build/test regressions from updated tooling.Overview
Updates
package-lock.jsonto bump dev/build tooling dependencies, notablyvite7.3.1→7.3.2, plus patch updates tobrace-expansionandpicomatch(including nested copies used byvite/tinyglobby).No application/source code changes; this is an npm audit-style lockfile refresh that may slightly affect build and test behavior due to updated toolchain versions.
Reviewed by Cursor Bugbot for commit 0bacdbb. Bugbot is set up for automated code reviews on this repo. Configure here.