Drop support for node < 4 - #53
Merged
Merged
Conversation
Member
|
@realityking thank you for the contribution. |
Contributor
Author
|
@bcoe This seems to have broken the build on master after merging. Is this common or should I dig into it? |
Member
|
@realityking yeah, it's weird that it broke on merge rather than on this branch. I would be tempted for you to look at whether it's string-width or strip-ansi -- I know there were a few things in the works around these libraries that could have potentially caused bugs in cliui. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This unblocks upgrades for some dependencies, enabling deduplication with
yargsagain.