Properly handle SSL errors and npm path resolution#24
Merged
Conversation
1. Fixed SSL exception handling - catch urllib.error.URLError instead of ssl.SSLError 2. Added proper npm path resolution on Windows: - Check for npm.cmd explicitly in Program Files\nodejs - Add detailed debug output to understand npm failures - Use full path to npm.cmd when needed 3. Improved error handling in run_command to show actual errors 4. Check for SSL/certificate strings in URLError to detect SSL issues correctly
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
1 participant
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.
No description provided.