deps: update deps and regenerate package-lock.json #225
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
lundibundi
approved these changes
Jun 20, 2017
Using the current `package-lock.json` (that was generated using npm@5.0.0 and then amended a couple of times with newer npm versions), npm generates a dependency tree that shows lots of errors in the `npm list` output. This commit regenerates the package tree with the latest npm version in order to resolve these problems.
aqrln
changed the title
|
Rebased to incorporate new package from |
aqrln
added a commit
that referenced
this pull request
Jun 22, 2017
Using the current `package-lock.json` (that was generated using npm@5.0.0 and then amended a couple of times with newer npm versions), npm generates a dependency tree that shows lots of errors in the `npm list` output. This commit regenerates the package tree with the latest npm version in order to resolve these problems. PR-URL: #225 Reviewed-By: Mykola Bilochub <nbelochub@gmail.com> Reviewed-By: Denys Otrishko <shishugi@gmail.com>
|
Landed in 54954b7. |
belochub
pushed a commit
that referenced
this pull request
Jan 22, 2018
Using the current `package-lock.json` (that was generated using npm@5.0.0 and then amended a couple of times with newer npm versions), npm generates a dependency tree that shows lots of errors in the `npm list` output. This commit regenerates the package tree with the latest npm version in order to resolve these problems. PR-URL: #225 Reviewed-By: Mykola Bilochub <nbelochub@gmail.com> Reviewed-By: Denys Otrishko <shishugi@gmail.com>
belochub
pushed a commit
that referenced
this pull request
Jan 22, 2018
Using the current `package-lock.json` (that was generated using npm@5.0.0 and then amended a couple of times with newer npm versions), npm generates a dependency tree that shows lots of errors in the `npm list` output. This commit regenerates the package tree with the latest npm version in order to resolve these problems. PR-URL: #225 Reviewed-By: Mykola Bilochub <nbelochub@gmail.com> Reviewed-By: Denys Otrishko <shishugi@gmail.com>
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.
Using the current
package-lock.json(that was generated usingnpm@5.0.0 and then amended a couple of times with newer npm versions),
npm generates a dependency tree that shows lots of errors in the
npm listoutput. This commit regenerates the package tree with the latestnpm version in order to resolve these problems.