Resolve npm dependency vulnerabilities#320
Merged
Merged
Conversation
crokita
approved these changes
Aug 16, 2023
Merged
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.
This PR is ready for review.
Risk
This PR makes no API changes.
Summary
This PR updates npm packages used by the project to resolve security vulnerabilities.
This PR removes references to the deprecated
requestpackage and instead uses the nativehttpslibrary.Additionally, the
npm installcommand will now need to be run asnpm install --legacy-peer-depsdue to a dependency conflict issue with some of the packages used by vue/cli. Trying to runnpm installon its own will fail.CLA