webpack-cli: Install fails behind corporate proxy (SSH block?)
Do you want to request a feature or report a bug? Feature request.
What is the current behavior?
Global install npm install -g webpack-cli
fails behind a corporate proxy. Error is:
Error: Command failed: git -c core.longpaths=true config --get remote.origin.url
I suspect that this is because our corporate proxy blocks SSH access to the internet (as many of them do).
What is the expected behavior? Install should not crash like this simply because SSH is unavailable.
If this is a feature request, what is motivation or use case for changing the behaviour?
We need an option to have the installer to execute its git clone
tasks via HTTPS instead of SSH. At the very least, the installer should trap this error and tell the user what the problem is.
Please mention other relevant information such as the browser version, Node.js version, Operating System and programming language. Windows 7, but it also happened on a Linux Mint VM behind the same corporate proxy.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 16 (9 by maintainers)
Possibly setting this option could help:
~/.gitconfig