Repository navigation
build(deps): update follow-redirects and vite for security fixes - #52
Merged
Merged
Conversation
Problem: npm audit reports a high severity issue in follow-redirects 1.16.0 (credential headers kept across cross-origin redirects), pulled in by wait-on through axios, and a moderate one in vite 6.4.3. Both are development tools only. Solution: update the lockfile to follow-redirects 1.16.1 and vite 6.4.4, within the ranges package.json already allows. npm update on the two packages, rather than npm audit fix, keeps every other entry unchanged.
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
2 participants
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.
Problem: npm audit reports a high severity issue in follow-redirects 1.16.0 (credential headers kept across cross-origin redirects), pulled in by wait-on through axios, and a moderate one in vite 6.4.3. Both are development tools only.
Solution: update the lockfile to follow-redirects 1.16.1 and vite 6.4.4, within the ranges package.json already allows. npm update on the two packages, rather than npm audit fix, keeps every other entry unchanged.