Package Details: hyper 3.2.3-2

Git Clone URL: (read-only, click to copy)
Package Base: hyper
Description: A terminal built on web technologies
Upstream URL:
Keywords: hyper hyper.js terminal
Licenses: MIT
Conflicts: hyperterm
Replaces: hyperterm
Submitter: aabmass
Maintainer: None
Last Packager: flakusha
Votes: 63
Popularity: 0.099224
First Submitted: 2016-10-10 16:38 (UTC)
Last Updated: 2022-06-13 09:32 (UTC)

Latest Comments

JaydenDev commented on 2022-07-22 21:43 (UTC)

i don't understand why this was orphaned, a new stable release hasn't even been released yet. I can assure you the maintainer will probably update this package when 3.3.0 releases.

flakusha commented on 2022-06-13 09:33 (UTC)

Hello! I have updated npm dependency for hyper, but I cannot manage the wayland environment patch at the moment (lack of spare time), orphaning the package for now. v3.3.0 is not stable at the moment so I cannot risk updating to it.

jtheoof commented on 2022-05-31 02:40 (UTC)

Also it would be nice to tweak a little the startup script by doing something similar as to what code is doing. This way we would be able to start hyper in a pure wayland environement by just playing with the electron-flags.conf file.

jtheoof commented on 2022-05-31 02:21 (UTC)

I believe the PKGBUILD is missing a makedpends on npm. I got an error at some point because I had not that package installed. Built without any issue after that.

jef commented on 2021-04-07 04:13 (UTC)

Latest builds: error: failed retrieving file 'npm-7.7.6-1-any.pkg.tar.zst'

bet4it commented on 2020-01-21 03:45 (UTC)

@hellopeach @rmx You can use hyper-git on AUR.

rmx commented on 2019-11-22 13:55 (UTC) (edited on 2019-11-22 14:02 (UTC) by rmx)

Installing with yay:

==> Sources are ready.
==> Making package: hyper 3.0.2-1 (2019-11-22T14:52:31 CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
app/renderer/bundle.js doesn't exist
==> Entering fakeroot environment...
==> Starting package()...
cp: cannot stat 'dist/linux-unpacked/*': No such file or directory
==> ERROR: A failure occurred in package().
Error making: hyper

hellopeach commented on 2019-10-25 04:32 (UTC) (edited on 2019-10-25 04:32 (UTC) by hellopeach)

The hyper terminal I installed from this AUR package with yay seems to be missing command line argument support? Commands like hyper install, hyper list, hyper version, etc. just launches hyper, while hyper --help shows the following message:

Hyper version 3.0.2
Hyper does not accept any command line arguments. Please modify the config file instead.
Hyper configuration file located at: ~/.hyper.js

Hyper 3.0.2 I installed on other platforms (Ubuntu, Windows, etc.) doesn't have this issue, any idea how to fix this?

bob418 commented on 2019-06-28 06:42 (UTC) (edited on 2019-06-28 06:45 (UTC) by bob418)

@DDoSolitary I use Manjaro KDE 18.0.4. It has version 2.1.2-1 listed in community packages. The packager is Stefano Capitani Every time when I run "sudo pacman -Syu", I get warning message:

warning: hyper: local (3.0.2-1) is newer than community (2.1.2-1)
 there is nothing to do

DDoSolitary commented on 2019-06-28 06:32 (UTC)

@bob418 I can't find the package in community

bob418 commented on 2019-06-28 02:13 (UTC) (edited on 2019-06-28 02:13 (UTC) by bob418)

It conflicts with the same-named package in community (2.1.2-1). I got the following message when trying to install it:

:: Retrieving package(s)...
hyper is available in community
:: failed to retrieve packages

However I could download the snapshot and run "makepkg -si" to install it.

bogdanbiv commented on 2019-05-19 22:38 (UTC) (edited on 2019-05-19 22:40 (UTC) by bogdanbiv)

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 (UTC)

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>].

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:

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-git package ¯_(ツ)_/¯

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

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 Aborting... ==> ERROR: Makepkg was unable to build hyper.

browsing the url returns 404: Not Found

aabmass commented on 2017-09-27 16:25 (UTC)


DDoSolitary commented on 2017-09-27 07:44 (UTC) (edited on 2017-09-27 07:44 (UTC) by DDoSolitary)

@aabmass Thank you very much, but could you please consider update to v2.0.4? That is the latest canary release now, and v2.0.3 fixes the really annoying resizing bug.

aabmass commented on 2017-09-27 04:52 (UTC)

I am just going to move the whole package version up to 2.0.2 since there is an out-of-date message in the app..

sistematico commented on 2017-09-23 03:58 (UTC) updated PKGBUILD

DDoSolitary commented on 2017-09-22 10:33 (UTC)

Hello, could you please create a package for the canary releases?

aabmass commented on 2017-06-26 18:16 (UTC)

@linarcx looks like didn't download correctly? Try rerunning and see if it is able to pass checksum match

linarcx commented on 2017-06-24 06:48 (UTC)

i got this error: Error: Generated checksum for "" did not match expected checksum. at ChecksumMismatchError.ErrorWithFilename (/tmp/packerbuild-1000/hyper/hyper/src/hyper-1.3.3/node_modules/sumchecker/build.js:41:124) at new ChecksumMismatchError (/tmp/packerbuild-1000/hyper/hyper/src/hyper-1.3.3/node_modules/sumchecker/build.js:56:133) at Hash.<anonymous> (/tmp/packerbuild-1000/hyper/hyper/src/hyper-1.3.3/node_modules/sumchecker/build.js:203:22) at emitNone (events.js:105:13) at Hash.emit (events.js:207:7) at emitReadable_ (_stream_readable.js:502:10) at emitReadable (_stream_readable.js:496:7) at addChunk (_stream_readable.js:263:7) at readableAddChunk (_stream_readable.js:239:11) at Hash.Readable.push (_stream_readable.js:197:10) info Visit for documentation about this command. ==> ERROR: A failure occurred in prepare(). Aborting... The build failed.

aabmass commented on 2017-06-19 16:10 (UTC)

@sindrenm Interesting that it works fine with makepkg. I don't think that it can be an issue with pacaur handling environment variables since it calls makepkg which always uses bash. I will try with pacaur and see if I can reproduce.

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:

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: 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.

aabmass commented on 2017-03-17 03:26 (UTC)

@dan0cat Why switch md5 to sha512? See :)

dan0cat commented on 2017-03-15 14:00 (UTC)

gconf is a dependency

dan0cat commented on 2017-03-15 13:58 (UTC) (edited on 2017-03-16 00:40 (UTC) by dan0cat)

Would be awesome if package verification could switch from md5 to sha512 ... I'm happy to help. I made the changes but can't commit, let me know if you'd like me to send the update PKGBUILD

materemias commented on 2017-02-18 09:51 (UTC)

@aabmass sure, 2nd try worked

aabmass commented on 2017-02-17 19:33 (UTC)

@materemias I saw that error when I was testing the build -- it is a checksum error on a downloaded file. I just built it fine again on my machine, try it again and see if it downloads correctly.

materemias commented on 2017-02-17 18:23 (UTC)

1.2.1-1 fails to build for me with error Failed at the electron-chromedriver@1.6.0 install script 'node ./download-chromedriver.js'.

aabmass commented on 2017-02-02 03:13 (UTC)

@bananaoomarang did you have an issue building? It doesn't really even need electron as a dep, since the build processes builds against and includes its own specific version of electron.

bananaoomarang commented on 2017-01-31 20:18 (UTC)

I think this should list `electron` as a `makedep`?

kveldulf commented on 2017-01-23 00:46 (UTC)

@aabmass yes, it's working, but it now gives a warning saying that the package contains a reference to $srcdir. what's that about?

aabmass commented on 2017-01-19 04:58 (UTC)

Alright, can you guys confirm its working now for you?

aabmass commented on 2017-01-19 04:47 (UTC)

@jekku and @Oak I opened an issue with hyper here I also think I found a work-around for now. I'll try and get that out soon.

Oak commented on 2017-01-19 04:17 (UTC)

Yaourt wanrs "==> WARNING: Package contains reference to $srcdir". After installation, hyper is not running, the output is: running in prod mode electron will open file:///usr/lib/hyper/resources/app/index.html

jekku commented on 2017-01-19 03:45 (UTC)

I have the same problem as @fixerfrasse. It doesn't continue on after trying to open the file. Sadly I'll have to change my terminal for now.

fixerfrasse commented on 2017-01-18 22:53 (UTC)

I successfully installed the package. But when I run 'hyper' it doesn't open any window. I can see a huge amount of processes that doesn't seem to do much but taking RAM. When running from terminal I get this message: running in prod mode electron will open file:///usr/lib/hyper/resources/app/index.html Any suggestions?

aabmass commented on 2017-01-16 15:56 (UTC)

@kveldulf actually, I just re-built hyper and I'm having the same issue. I'll look into it.

aabmass commented on 2017-01-16 15:40 (UTC)

@nicoulaj that's interesting. I'll change %40 to @. Thanks for your help

aabmass commented on 2017-01-16 15:36 (UTC)

@kveldulf what happens when you run "hyper" in a terminal?

kveldulf commented on 2017-01-15 19:53 (UTC)

@aabmass When I install Hyper using yaour, I click the application icon and it doesn't open. I can't get it to work at all.

nicoulaj commented on 2017-01-13 17:24 (UTC)

@aabmass If you change the "%40" to "@" in the PKGBUILD, both methods work fine (curl and wget).

nicoulaj commented on 2017-01-13 17:18 (UTC) (edited on 2017-01-13 17:20 (UTC) by nicoulaj)

@aabmass I solved it, it was due to changing the DLAGENTS from curl to wget in makepkg.conf... wget changed the "%40" into "@" in the file name, whereas curl keeps it...

aabmass commented on 2017-01-12 15:13 (UTC)

@nicoulaj that's interesting, it calculates the checksum and compares it fine for me. Did the file actually download?

nicoulaj commented on 2017-01-12 14:37 (UTC)

Yaourt complains for me that it's missing the checksum for the PNG image: ==> Validation des fichiers source avec md5sums... 1.1.0.tar.gz ... Réussite Hyper-Mark-120%403x.png ... INTROUVABLE Hyper.desktop ... Réussite I guess this is due to the encoded (%40) character...

aabmass commented on 2017-01-12 02:54 (UTC)

@fdidron What version of yarn do you have installed? And what architecture? You're the second person to have an issue with yarn so I'll have the package just use npm for now.

commented on 2017-01-12 00:41 (UTC)

I'm having the following issue installing v1.1.0 using yarn : Error trace available here: A workaround for the time being is removing yarn prior to install so the deps are installed with npm. Kind regards, Florian

aabmass commented on 2017-01-11 17:27 (UTC)

Sorry for the slow updates everyone, working on it now. @konstantin The pkgbuild does use npm if yarn isn't available. So, for most people it will just use npm. Yarn downloads the deps much faster if it is available, that's the only reason I added it. Tell me if you have any more problems!

rakmial commented on 2017-01-10 20:22 (UTC)

1.1.0 is out now

konstantin commented on 2016-12-31 19:32 (UTC) (edited on 2016-12-31 19:43 (UTC) by konstantin)

Can you change to "npm install" for now? Cause yarn doesn't install 7zip-bin-linux.(from deps of electron-builder) UPDATE: actually current yarn version(0.18.1) installs correctly, but it is still better to use npm instead of checking yarn version(cause yarn isn't available from arch repos) Can you also update pkgversion to 1.0.1 md5: 826b301878e89383b1c432f01dc9ee8e Thank you!

graczykr commented on 2016-12-15 20:33 (UTC)

@aabmass: I have already uninstalled it but as far as I can recall the problem arose at runtime.

aabmass commented on 2016-12-13 04:44 (UTC)

@graczykr does it complain at runtime or build-time?

graczykr commented on 2016-12-05 22:04 (UTC)

This may be a recent change, but installing it today (05.12.2016) the package seems to depend on gconf; with the latter not present, it complains about missing. Maybe this should be added to the dependency list.

BunBum commented on 2016-11-23 20:06 (UTC)

@aabmass yes base-devel is installed. Previous versions of this package worked fine. The error occurred since the last update. With hyper 0.8.3-2 I get the error that g++ could not be found. I'm using Node in version v7.1.0

aabmass commented on 2016-11-18 21:21 (UTC)

@BunBum have you installed the base-devel group?

BunBum commented on 2016-11-17 20:34 (UTC)

With the latest version I get a > child_pty@3.0.1 install /tmp/yaourt-tmp-me/aur-hyper/src/hyper-0.8.3/app/node_modules/child_pty > node-gyp rebuild make: Entering directory '/tmp/yaourt-tmp-me/aur-hyper/src/hyper-0.8.3/app/node_modules/child_pty/build' CXX(target) Release/ make: Leaving directory '/tmp/yaourt-tmp-me/aur-hyper/src/hyper-0.8.3/app/node_modules/child_pty/build' Error output: make: g++: Command not found make: *** [ Release/] Error 127

aabmass commented on 2016-11-16 04:35 (UTC)

Alright, you should be able to build it now with the patch I added. @duckbrain I also just fixed that symlink -- thanks for the heads up! (They renamed the binary)

aabmass commented on 2016-11-16 04:17 (UTC)

@aleksijohansson looks like that just got fixed I may have to make a patch for that

aleksijohansson commented on 2016-11-14 18:22 (UTC)

I have an issue installing this package, this is what I get: ERROR in Entry module not found: Error: Can't resolve 'babel'

duckbrain commented on 2016-11-12 07:25 (UTC)

@aabmass: The Symlink at /usr/bin/Hyper points to "../lib/hyper/Hyper", but the binary is located at /usr/lib/hyper/hyper (with a lowercase 'H'). This is done on line 58 of the PKGBUILD.

aabmass commented on 2016-11-08 05:29 (UTC)

@hshin23 Hey, I'm not seeing that typo. Mind elaborating? Thanks!

hshin23 commented on 2016-11-05 19:08 (UTC)

You have a typo. Change to ln -s ../lib/hyper/hyper instead of ../lib/hyper/'H'yper

aabmass commented on 2016-10-10 21:13 (UTC)

I created the hyper package and this will be merged into it.

aabmass commented on 2016-10-10 15:30 (UTC)

@auk awesome! I'll add it in to the pkgbuild and hopefully get this renamed to hyper in the next few days

auk commented on 2016-10-09 22:34 (UTC)

@aabmass Hmm...definitely sounds strange! Hopefully the mods can be of help. I'm not familiar enough with the AUR to offer any suggestions with that. Unrelated, but I made a desktop entry file for Hyper: will see if it's something I can contribute to zeit/hyper to make it easier for us to use here

aabmass commented on 2016-10-08 03:37 (UTC)

Okay, so now even though there is currently no "hyper" package in the AUR, I can't push to git+ssh:// It looks like there used to be a "hyper" package -- cloning git+ssh:// doesn't give a bare repository! It looks like the PKGBUILD for some old package. Seems like an AUR bug..

aabmass commented on 2016-10-08 03:10 (UTC) (edited on 2016-10-08 03:11 (UTC) by aabmass)

@auk thanks for the patch! I applied it. Unfortunately I can't push to the AUR if I the package is renamed like that. I'll submit a request to the AUR mods to rename it and then I'll change the pkgname (I left comments). I'm not 100% sure how the process works.

auk commented on 2016-10-07 23:08 (UTC)

Hi Aaron. Here's a patch that upgrades this package to v0.8.1: There are three files in that gist: - 0001-Update-to-Hyper-v0.8.1.patch -- patch generated with `git format-patch` - PKGBUILD.diff -- diff generated with `git diff` - PKGBUILD -- the modified PKGBUILD I also removed the `autohide-menu.patch` in favor of tomru's hyperterm-hidemenu plugin ( In case you'd like to rename this package to "hyper", I filled out the PKGBUILD's "replaces" and "conflicts" fields. Hope this helps! Thank you for all your work and maintaining this package. For posterity, here's the release info for v0.8.1:

aabmass commented on 2016-10-07 15:54 (UTC)

Looks like they renamed to just hyper...

aabmass commented on 2016-09-15 03:02 (UTC)

@tomru I agree, didn't realize the reason for this bug is accommodating menubar at top WM's -- thought it was an overall linux problem.

tomru commented on 2016-09-14 21:26 (UTC)

tbh, I'm not sure this patch should be part of the PKGBUILD. What if someone is crazy enough to use Unity (i.e. having the menubar at the top of the window, like osx)? Just published a super tiny plugin that you can use if the menu bar is in your way.

aabmass commented on 2016-09-12 15:35 (UTC)

Thanks @fleischie and @bounb. I updated the PKGBUILD with your changes @fleischie, thanks for the patch!

fleischie commented on 2016-09-12 13:40 (UTC)

@aabmass @bounb The following gist contains the patch as well as the updated PKGBUILD: I had to change the PKGBUILD slightly, because the download-URL for the hyperterm source wasn't available. Additionally I added the file to the `sources` and it's md5sum to the md5sums (via `updpkgsums`). (Sorry for responding so late.)

bounb commented on 2016-09-04 23:03 (UTC)

@aabmass the screenshots are on mac OS, where the menu bar behaves differently. I guess this is one reason why there is no official build for linux yet. the relevant issue is here

aabmass commented on 2016-09-03 00:49 (UTC)

@fleischie Hey! I was actually wondering about the menubars... It seems like they shouldn't be visible at all going by the screenshots here: If the menu isn't how its supposed to look, you could probably submit the patch in a pull request to the project. Do you mind posting a link to a gist or pastebin of your patch?

fleischie commented on 2016-09-03 00:34 (UTC)

Hi @aabmass, thanks for the PKGBUILD. :) I have a request, of which I am not sure, whether it is valid/feasible: I like to autohide my electron menubars, thus I have created a patch for a specific file in the hyperterm sources. My question is: Could this possibly break the default behavior (or be inconvenient for anybody)? How do I submit the patch to you resp. the changes as a whole? Is there anything I should consider before submitting a patch? Thank you for your time. :)

aabmass commented on 2016-08-31 04:19 (UTC)

@jeysal Thanks for trying that out! I'll update the PKGBUILD then. I didn't see it was an optional dependency!

jeysal commented on 2016-08-30 17:12 (UTC)

yes, just adding the python2 makedepend works for me, since node-gyp searches for a 'python2' executable over a 'python' executable. BTW npm has a dependency "python2 (optional) - for node-gyp". I assume its optional because 99% of npm users will never use node-gyp.

aabmass commented on 2016-08-29 14:22 (UTC)

@jeysal yes, it's just that installing npm with pacman provides the node-gyp binary which doesn't depend on python2: $ pkgfile `which node-gyp` community/npm I'm also confused because I didn't have to run 'npm config set python /usr/bin/python2' to get it building. Were you able to build by just adding python2 to makedepends and then building without the npm config command?

jeysal commented on 2016-08-29 14:12 (UTC)

@aabmass npm itself and 99% of the relevant npm packages do not require python2 in any way. It's node-gyp (which is used during the hyperterm build) that requires a python2 binary. See

aabmass commented on 2016-08-17 16:52 (UTC)

@jeysal that's pretty weird that its not in the dependencies for arch's npm pacakge then. I didn't ever have to point npm to /usr/bin/python2 either.

jeysal commented on 2016-08-14 17:45 (UTC)

I had the same error as bkuri, for me the problem was that node-gyp requires python 2 but only 3 was installed. I resolved the problem by adding 'python2' to makedepends and running 'npm config set python /usr/bin/python2' right before 'npm install' as suggested in node-gyp's README.

aabmass commented on 2016-08-11 14:39 (UTC)

@basil You can run the binary "HyperTerm"

basil commented on 2016-08-11 12:04 (UTC)

How would I start this after installing?

aabmass commented on 2016-08-09 02:43 (UTC)

@sukso96100 Yep, my bad! Updating

sukso96100 commented on 2016-08-08 03:37 (UTC)

HI! I think the license should be MIT not GPL.

aabmass commented on 2016-08-05 00:45 (UTC)

For whoever flagged this out of date, electron-bin provides electron. You could install this and be able to run this pkgbuild.

aabmass commented on 2016-08-05 00:44 (UTC)

Hey bkuri, are you still having this problem?

bkuri commented on 2016-08-02 00:28 (UTC)

I'm getting this error after installation: ```sh A native module failed to load. Typically this means you installed the modules incorrectly. Use `scripts/` to trigger the installation. More information: running in prod mode electron will open file:///usr/lib/hyperterm/resources/app/index.html session not found by null ``` I also get the following error dialog: Hope this helps.

aabmass commented on 2016-07-26 20:55 (UTC)

Thanks, tomru! Ya, it looks like they changed the build system, I'll take a look when I get home

tomru commented on 2016-07-26 20:45 (UTC)

Hiya @aabmass, lol - 4 days ago and we are at v0.7.1 - the thing is on fire. For a suggestion to bump this to v0.7.1 see cheers