quine-global/hyper
1
0
Fork 0
mirror of https://github.com/quine-global/hyper.git synced 2026-01-15 13:18:40 -09:00
Code Issues Projects Releases Packages Wiki Activity Actions

Use yarn for everything

Browse source
This commit is contained in:
Matheus Fernandes 2017-02-23 18:02:53 -03:00
parent d9fe948672
commit d521e8e162
No known key found for this signature in database
GPG key ID: DD07CA4EA7B65C4F
3 changed files with 11 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
.travis.yml
View file

@ -31,11 +31,8 @@ before_install:
install: install:
- yarn - yarn
before_script:
- npm prune
after_success: after_success:
- npm run dist - yarn run dist
branches: branches:
except: except:

9
appveyor.yml
View file

@ -9,12 +9,11 @@ environment:
image: Visual Studio 2015 image: Visual Studio 2015
init: init:
- npm config set msvs_version 2015 # we need this to build `pty.js` - yarn config set msvs_version 2015 # we need this to build `pty.js`
install: install:
- ps: Install-Product node 6 x64 - ps: Install-Product node 6 x64
- set CI=true - set CI=true
- npm -g install npm@latest
- yarn - yarn
build: off build: off
@ -23,9 +22,9 @@ shallow_clone: true
test_script: test_script:
- node --version - node --version
- npm --version - yarn --version
- npm run test - yarn run test
on_success: on_success:
- npm run dist - yarn run dist
- ps: ls .\dist\win\*.exe | % { Push-AppveyorArtifact $_.FullName } - ps: ls .\dist\win\*.exe | % { Push-AppveyorArtifact $_.FullName }

12
readme.md
View file

@ -28,16 +28,16 @@ choco install hyper
1. Install the dependencies 1. Install the dependencies
* If you are running Linux, install `icnsutils`, `graphicsmagick`, `xz-utils` and `rpm` * If you are running Linux, install `icnsutils`, `graphicsmagick`, `xz-utils` and `rpm`
* If you are running Windows, install `windows-build-tools` with `npm i -g windows-build-tools`. * If you are running Windows, install `windows-build-tools` with `yarn global add windows-build-tools`.
2. [Fork](https://help.github.com/articles/fork-a-repo/) this repository to your own GitHub account and then [clone](https://help.github.com/articles/cloning-a-repository/) it to your local device 2. [Fork](https://help.github.com/articles/fork-a-repo/) this repository to your own GitHub account and then [clone](https://help.github.com/articles/cloning-a-repository/) it to your local device
3. Install the dependencies: `npm install` 3. Install the dependencies: `yarn`
4. Build the code and watch for changes: `npm run dev` 4. Build the code and watch for changes: `yarn run dev`
5. In another terminal tab/window/pane, run the app: `npm run app` 5. In another terminal tab/window/pane, run the app: `yarn run app`
To make sure that your code works in the finished application, you can generate the binaries like this: To make sure that your code works in the finished application, you can generate the binaries like this:
```bash ```bash
npm run dist yarn run dist
``` ```
After that, you'll see the binary in the `./dist` folder! After that, you'll see the binary in the `./dist` folder!
@ -45,7 +45,7 @@ After that, you'll see the binary in the `./dist` folder!
### node-pty issues ### node-pty issues
If after building during development you get an alert dialog related to `node-pty` issues, If after building during development you get an alert dialog related to `node-pty` issues,
make sure its build process is working correctly by running `npm run rebuild-node-pty`. make sure its build process is working correctly by running `yarn run rebuild-node-pty`.
If you're on macOS, this typically is related to Xcode issues (like not having agreed If you're on macOS, this typically is related to Xcode issues (like not having agreed
to the Terms of Service by running `sudo xcodebuild` after a fresh Xcode installation). to the Terms of Service by running `sudo xcodebuild` after a fresh Xcode installation).