Update Inquirer and Caporal #45
Merged
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
Throw errors when attempting to render prompts in non-interactive environments.
jhorbulyk
requested review from
kirill-levitskiy and
A3a3e1
and removed request for
kirill-levitskiy
A3a3e1
approved these changes
Feb 20, 2020
jhorbulyk
added a commit
that referenced
this pull request
Feb 24, 2020
* Add option for more verbose logging on uncaught exceptions (#45) * Throw errors when attempting to render prompts in non-interactive environments.
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.
environments.
Some updates were required in some downstream dependencies. There are PRs to fix these issues:
However, they haven't been merged and it's not clear when they will be merged. For the moment, I've just pointed to eio GitHub repos with commit IDs (as opposed to publishing shadow packages). For inquirer, the root of the GitHub repo isn't the location of the correct npm package.json, so I've solved this problem by adding a post install script to create a file which acts as a link. It's a dirty hack but it works...