This repository was archived by the owner on Sep 17, 2025. It is now read-only.
Fixing NPM Vulnerabilities #72
Merged
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.
Finally, could have fixed it:
lodashand replaced with built-in functionalities;always-tailsince no need for that;gruntversion from0.4.5to1.0.3;grunt-mocha-cliversion from2.0.0to4.0.0;grunt-mocha-cliis using[email protected], I had to modify the test suites to support[email protected]-Mochahad new and core changes inv3.0.0and newer versions listed here and here -[email protected]is using[email protected]and havinghighandcriticalvulnerabilities;npm audit fix(afternpm installand havingpackage-lock.json) says there is no vulnerability at all.Tested on
Node v6.10.2andNPM v6.4.1.