Gracefully handle npm install error gracefully (close #1168) #1171
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
LinusBorg
changed the title
|
Damn, it seem #1170 might fix the underlying reason, and it was easy so find. I will close this PR, and push another one rebased on that fix. |
This pull request was closed.
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 problem
See #1168
what does this PR do
When the user has chosen to let the template automatically install dependencies, and that call to
npm installfails, We now display a usefull error message with instructions on how to proceed.Is that a perfect solution?
Not really, but it helps to proceed even if autoInstall fails.
If someone for whom this process fails would be willing to investigate, that would be much apprechiated. Since I can't reproduce the error from #1168, I don't know how to debug this.
To test this PR:
I'm mentioning some folks who have previously reported this error with the request to test this workaround/solution on their systems:
Thanks!