Package Details: hyper 3.0.2-1

Git Clone URL: (read-only)
Package Base: hyper
Description: A terminal built on web technologies
Upstream URL:
Keywords: hyper hyper.js
Licenses: MIT
Conflicts: hyperterm
Replaces: hyperterm
Submitter: aabmass
Maintainer: aabmass (blind)
Last Packager: blind
Votes: 57
Popularity: 1.315069
First Submitted: 2016-10-10 16:38
Last Updated: 2019-05-10 14:10

Latest Comments

1 2 3 4 5 6 ... Next › Last »

bogdanbiv commented on 2019-05-19 22:38

I get this weird error: gyp: Call to 'node -e "require('nan')"' returned exit status 0 while in binding.gyp. while trying to load binding.gyp

However, I have already installed nan globally just before. Please check this log for further details:

So, what am I missing, please?

$ sudo npm install -g cross-env gyp nan
[sudo] password for bogdanbiv: 
/usr/bin/cross-env -> /usr/lib/node_modules/cross-env/dist/bin/cross-env.js
/usr/bin/cross-env-shell -> /usr/lib/node_modules/cross-env/dist/bin/cross-env-shell.js
+ gyp@0.5.0
+ cross-env@5.2.0
+ nan@2.14.0
added 22 packages from 25 contributors in 4.44s

ionlights commented on 2018-11-03 15:23

Am getting:

Failed to symlink Hyper CLI { Error: EACCES: permission denied, symlink '/usr/lib/hyper/resources/bin/hyper' -> '/usr/local/bin/hyper'
  errno: -13,
  code: 'EACCES',
  syscall: 'symlink',
  path: '/usr/lib/hyper/resources/bin/hyper',
  dest: '/usr/local/bin/hyper' }

Fix appears to be: ln -s /usr/lib/hyper/resources/bin/hyper /usr/local/bin/hyper

  • This happens immediately post installation and appears whenever you run hyper [<args>].

LenticularAu commented on 2018-09-19 18:27

Electron build fails to complete the task and therefore returns an error making it impossible to install using both Yay and Trizen as of what I've tried. Please fix this problem. More information can be found using the following link:

major commented on 2018-07-19 14:48

My build is hangs for around 4-5 minutes at electron-chromedriver, and then the buid fails. Earlier, the it wasn't able to install Nodejs, which I had to install manually. Is this some bug, or some problem from my side?

P.S. I tried the same on another machine, and it hangs at electron-chromedriver again.

MarkPitman commented on 2018-05-01 20:16

aabmass and I agree, this package will follow stable releases only. I am going to unflag the package. If someone wants to follow canary builds, maybe fork this package and create a hyper-git package ¯_(ツ)_/¯

MarkPitman commented on 2018-04-24 20:38

Now that 2.x.x is mainline, should we create separate package that tracks the post 2.x.x canary builds?

MarkPitman commented on 2018-04-06 22:49

If you have problems building it may be because you have npm 5.8.0 installed. Downgrading to npm 5.7.1 should solve the problem.

npm -i -g npm@5.7.1

aabmass commented on 2017-12-24 03:37

Hey guys , sorry for the slow update. I updated the pkgbuild and I'm just using the canary versions since the "latest release" is pretty old. Also, hoping that your AUR wrappers detect the update even though the pkgver is now lower alphabetically..

rakmial commented on 2017-12-13 22:54

@DDoSolitary is correct, package was able to build after modifying pkgver variable in PKGBUILD. You'll need to find $pkgver in the functions and replace it with ${pkgver//_/-} to deal with the hyphen.

The md5 checksum is obviously going to be a problem too. Using yaourt, I did:

yaourt -Syua --m-arg "--skipchecksums" hyper

DDoSolitary commented on 2017-12-08 13:23

It seems that the project has changed naming strategy of prereleases and all the v2.x releases have been renamed to 2.0.0-canary.x. Now the latest release is 2.0.0-canary.8 so the download URL should be changed to