Package Details: hyper 3.4.1-1

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.000057
First Submitted: 2016-10-10 16:38 (UTC)
Last Updated: 2023-01-10 08:41 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 12 Next › Last »

sindrenm commented on 2017-06-10 23:49 (UTC)

I can confirm having the same issue as @Heziode when installing using pacaur. However, downloading the snapshot and installing with makepkg works fine. I'm guessing it's an issue with how pacaur handles environment variables, then, and your package is fine. :-)

aabmass commented on 2017-05-25 17:49 (UTC)

@Heziode Do you have the output of makepkg? cross-env shouldn't need to be a pacman dependency since hyper's package.json pulls it in. The PKGBUILD adds the node_modules/.bin folder to path and cross-env should be in there.

Heziode commented on 2017-05-25 17:42 (UTC)

Little issue, when I try to install this package, I've a build error because "cross-env" it's didn't install. Solved with "npm install -g cross-env", but it can be added in dependencies of this package?

aabmass commented on 2017-05-13 00:13 (UTC)

Should be fixed now, and bumped to 1.3.3. Note that hyper will say that you can upgrade to 1.3.3 but that is because they forgot to bump the version in their release: https://github.com/zeit/hyper/issues/1818

aabmass commented on 2017-05-12 23:56 (UTC)

Hey thanks guys. I see the problem and I'll fix it!

nicoulaj commented on 2017-05-12 18:57 (UTC)

@aabmass @fluffynun same error here.

fluffynun commented on 2017-05-12 15:05 (UTC)

@aabmass I keep getting this error on build: https://gist.github.com/ceesco53/91ec7192fab111a09504045debbf92df 1.3.1 builds fine. 1.3.2 is where the poop hits the oscillating device for me ;)

aabmass commented on 2017-03-18 04:57 (UTC)

@dan0cat no worries :)

dan0cat commented on 2017-03-18 04:48 (UTC)

You're right. I didn't read the Integrity section before my fingers started typing. My bad.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 12 Next › Last »