npm -E audit fix in prep for 2.4 release #521
Merged
Conversation
This file contains 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
|
I hated to do this, but the previously mentioned PR #512 wasn't building. I also had run FYI, this is the last remaining item before cutting |
mickmister
approved these changes
Apr 14, 2020
levb
approved these changes
Apr 14, 2020
This was referenced Apr 14, 2020
Closed
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The following PR (#512) was originally created to update npm packages but has also broken the build. This is a fresh PR to update off of the latest master build.
The command that has been run is
npm -E audit fixwhich updates security issues.-Eis short for--save-exact