Hyper: Cannot update plugins

Created on 17 Feb 2017  ·  6Comments  ·  Source: vercel/hyper

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

  • OS version and name: OS X El Capitan (10.11.6)

  • Hyper.app version: 1.2.1 (1.2.1.1528)
  • Link of a Gist with the contents of your .hyper.js: https://gist.github.com/Jamesking56/2836782ef1bd91403df720752cc9c730
  • Relevant information from devtools _(CMD+ALT+I on Mac OS, CTRL+SHIFT+I elsewhere)_: N/A
  • The issue is reproducible in vanilla Hyper.app: Was doing it before I installed plugins too.

Issue

When I run Hyper terminal, I get a notification:

Error updating plugins. Check `~/.hyper_plugins/npm-debug.log` for more information.

When I look for npm-debug.log it doesn't exist in that directory.

The same error also appears when clicking Plugins -> Update All Now

👯‍♀️ Is Duplicate

Most helpful comment

@Jamesking56 I was having this exact same issue. As @henrikdahl mentioned in #1513, a temporary fix is to set your shell of choice in the config file. I set mine to shell: 'bash' and everything seems to be working fine now.

All 6 comments

Duplicate #1513

@Jamesking56 I was having this exact same issue. As @henrikdahl mentioned in #1513, a temporary fix is to set your shell of choice in the config file. I set mine to shell: 'bash' and everything seems to be working fine now.

Set mine to shell: 'zsh' and all is well. Thanks!

I use Windows 10 Build 14393.693 and Hyper 1.2.1 and shell: 'C:\\Windows\\System32\\cmd.exe', in .hyper.js config file fix startup error http://imgur.com/a/e1cid Error updating plugins

@Jamesking56 the solution will be:

  • Go to another terminal app, and type echo $0. Take note of the returned output.
  • Go back to HyperTerm, ignoring all those errors. Open your file .hyper.js, scroll down to shell: '',, and replace it with what was outputted from above.
  • Quit HyperTerm and Run it again, you should receive no more errors.

Please see Issue #312, I have #anchored the solution for you there.

Closing as a duplicate of #1513. The fix for this bug will be released very soon.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

fabdelgado picture fabdelgado  ·  102Comments

mrjones2014 picture mrjones2014  ·  64Comments

b0rski picture b0rski  ·  66Comments

amilajack picture amilajack  ·  48Comments

deepsweet picture deepsweet  ·  47Comments