Fix #108 - Bumping up mkdirp version to 0.5.5 #109
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.
Hi!
I see that in PR #101 you bumped-up the version of
mkdirp
to 0.5.5 which in turn updatesminimist
to 1.2.5which addresses https://www.npmjs.com/advisories/1179
Problem is that this PR only updated
package-lock.json
and notpackage.json
that remains at 0.5.1. Aspackage.json
still depends onmkdirp
0.5.1, when we getnode-portfinder
as a dependency, we still get an old version ofminimist
.