Upgrade yargs to v13
#158
Merged
Upgrade yargs to v13
#158
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
The goal is to clean a warning harmless though annoying with a transitive dependency (mem). For details, see https://github.com/yargs/yargs PR #1270
|
v13 drops Node 6, which we currently still support, so this is currently blocked until we drop support |
|
unblocked by #160 |
This was referenced Jan 7, 2020
This was referenced Jan 21, 2020
This was referenced Feb 4, 2020
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.
The goal is to clean a (harmless) warning for a transitive dependency (
mem). The fix inyargsis in PR #1270 (https://github.com/yargs/yargs).This PR upgrades
yargsfrom v11 to v13.Useful links
Here are
yargsbreaking changes for: