chore(lockfile): update yarn.lock due to nodejs/node#20285 #6225
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
|
|
Unfortunately due to age of some entries in previous lockfile and many incompatibilities with newer packages versions after regeneration I am forced to ditch the idea to fix that issue. |
|
This problem will presumably be resolved with this PR as well, which updates to Gulp v4: #6143 |
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
Currently Yarn just after checkout and install cannot be build on Node 10 due to
gulp@3.9.xrelated bug: nodejs/node#20285.It seems like there are some old references in currently commited
yarn.lockfile and after proceeding as mentioned in issue linked above (regenerating lockfile) problem disappeared.