Quine's fork of "Hyper" by Vercel, A terminal built on web technologies
Find a file
Vladimir Starkov 7d05d0f148 increase timeout for update checks (#928)
* increase timeout for update checks

It seems like, there are lots of them and GitHub is not happy.
So increasing timeout 6x should fix that. In the end there is no need
to check updates every 5 minutes.

Fix #880

* restore check updates on start
2016-10-29 13:14:39 +02:00
.github Create github templates (#919) 2016-10-22 02:34:44 +01:00
app increase timeout for update checks (#928) 2016-10-29 13:14:39 +02:00
assets Reorg (#386) 2016-07-24 10:59:21 -07:00
build implement extend-info for the custom plist [@lordgiotto] 2016-07-24 11:13:25 -07:00
lib Change URL regex - fixes #867 (#943) 2016-10-29 13:13:53 +02:00
test fix tests 2016-10-06 08:33:07 -07:00
.editorconfig Fix for markdown files (#618) 2016-08-14 21:10:41 +02:00
.gitignore These aren't needed 2016-09-15 09:47:37 +02:00
.npmrc Split Panes (#693) 2016-10-03 19:00:50 -07:00
.travis.yml Run the one tests that exists in Travis before a release (#779) 2016-10-14 13:40:32 -05:00
LICENSE.md Add a copy of the MIT license (#160) 2016-07-16 18:24:53 -07:00
package.json Comply to XO's no-warning-comments rule 2016-10-25 15:04:37 +02:00
README.md Make "Art" link to hyper dir in the art repo 2016-10-16 18:50:53 +02:00
webpack.config.js Fix xo 0.17 errors and use root xo config for app (#859) 2016-10-12 20:35:44 -05:00

Build Status Slack Channel Changelog #213 XO code style

For more details, head to: https://hyper.is

Usage

You can download the latest release here.

If you're on macOS, you can also use Homebrew Cask to download the app by running these commands:

$ brew update
$ brew cask install hyper

Contribute

  1. If you are running Linux, install "icnsutils", "graphicsmagick" and "xz-utils"
  2. Fork this repository to your own GitHub account and then clone it to your local device
  3. Install the dependencies: npm install
  4. Build the code, watch for changes and run the app: npm start

To make sure that your code works in the finished application, you can generate the binaries like this:

$ npm run pack

After that, you'll see the binary in the ./dist folder!