Search Criteria
Package Details: hyper 3.4.1-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/hyper.git (read-only, click to copy) |
|---|---|
| Package Base: | hyper |
| Description: | A terminal built on web technologies |
| Upstream URL: | https://hyper.is/ |
| Keywords: | hyper.js terminal |
| Licenses: | MIT |
| Conflicts: | hyperterm |
| Replaces: | hyperterm |
| Submitter: | aabmass |
| Maintainer: | eclairevoyant |
| Last Packager: | eclairevoyant |
| Votes: | 64 |
| Popularity: | 0.000061 |
| First Submitted: | 2016-10-10 16:38 (UTC) |
| Last Updated: | 2023-01-10 08:41 (UTC) |
Dependencies (7)
- alsa-lib
- electron20AUR (electron20-binAUR)
- gtk3 (gtk3-ubuntuAUR, gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classic-xfceAUR, gtk3-classicAUR)
- libxss
- nss (nss-hgAUR)
- npm (corepackerAUR) (make)
- yarn (corepackerAUR, yarn-pnpm-corepackAUR, yarn-berryAUR) (make)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 .. 12 Next › Last »
<deleted-account> commented on 2018-09-19 18:27 (UTC)
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: https://pastebin.com/qkAWSmRm
major commented on 2018-07-19 14:48 (UTC)
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 (UTC)
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-gitpackage ¯_(ツ)_/¯MarkPitman commented on 2018-04-24 20:38 (UTC)
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 (UTC)
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 (UTC)
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 (UTC)
@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 (UTC)
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 https://github.com/zeit/hyper/archive/2.0.0-canary.8.tar.gz.
bugman commented on 2017-12-08 11:14 (UTC)
It seems that the download url is no more valid, trying to install it via yaourt got this error:
==> ERROR: Failure while downloading https://github.com/zeit/hyper/archive/2.1.1.tar.gz Aborting... ==> ERROR: Makepkg was unable to build hyper.
browsing the url returns 404: Not Found
« First ‹ Previous 1 2 3 4 5 6 7 8 .. 12 Next › Last »