Cannot Install Plugins/Themes with CLI

• I am on the latest Hyper.app version
• I have searched the issues of this repo and believe that this is not a duplicate

• OS version and name: macOS Sierra 10.12.6
• Hyper.app version: 2.0.0
• Link of a Gist with the contents of your .hyper.js: .hyper.js
• Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere): N/A
• The issue is reproducible in vanilla Hyper.app: Yes, this is an issue with the CLI.

Issue

Whenever I try to install anything with $ hyper install I get the following error:

unable to verify the first certificate
Plugin check failed. Check your internet connection or retry later.

I am using a school computer behind a firewall, and in the past, I have had the same problems with npm and apm. With those two cases, I was able to fix the issue by running [cmd] config set strict-ssl false, but there is no way of doing this with hyper.

I created this same issue in hpm, back when that was relevant, but never got a response.

Update

I now use NODE_EXTRA_CA_CERTS (yay), but Hyper doesn’t honour this, as @jerquiaga points out.

[albinekb]

We’re using a rebuilt version of yarn to install plugins.

I don’t think there’s enough demand for such a setting that it would be worth adding and maintaining.

There is a workaround:

1. Add plugin to ~/.hyper.js
2. Open terminal and cd ~/.hyper_plugins/
3. Install via your low security npm npm install
4. Plugins should work

Hope that helps 👍

Also sounds like your school is intercepting your traffic via a custom SSL cert, I would try everything to get around that, they are decrypting your traffic and can get all your passwords and everything you send on the webs…

[ghost]

Sure disabling is not a good idea. Introducing the functionality to add a custom CA would be the preferred way. However, how does a VPN solves the problem? I assume most people using hyper are devs or other IT guys working in a Company with a certain policy which are most likely neither allowed to build a vpn outside the company network, nor wiling to do such an affort for a “plugin”