Mailspring/packages/client-app/build
Evan Morikawa 1f2370c2a9 [client-app] run windows build separately
Summary:
build-client, aka packaging, aka bundling is now separate from uploading.
This is both to compartmentalize our tasks a bit more and so we can add a
non-grunt windows task inbetween packaging and uploading.

No more heavily-overloaded PUBLISH_BUILD flag.
Added SIGN_BUILD flag instead.
No more TRAVIS and TRAVIS_PULL_REQUEST flag.

Test Plan: Manual

Reviewers: halla, juan, spang

Reviewed By: juan, spang

Differential Revision: https://phab.nylas.com/D4208
2017-03-13 15:48:45 -07:00
..
config [*] move to monorepo 2017-02-16 18:46:26 -08:00
docs_templates [client-*] Rename packages folders and update readme 2017-02-16 13:31:37 -08:00
resources fix(linux-build): Update rpm spec to use new package name 2017-02-16 16:58:27 -08:00
tasks [client-app] run windows build separately 2017-03-13 15:48:45 -07:00
create-signed-windows-installer.js [client-app] run windows build separately 2017-03-13 15:48:45 -07:00
Gruntfile.js [client-app] run windows build separately 2017-03-13 15:48:45 -07:00
README.md [client-*] Rename packages folders and update readme 2017-02-16 13:31:37 -08:00

N1 Build Environment

Node version 0.10.x (Due to the version of electron currently used.)

N1 Building and Tasks

This folder contains tasks to create production builds of N1

Tasks should not be executed from this folder, but rather from /scripts. The /scripts folder has convenient methods that fix paths and do environment checks.

Note that most of the task definitions are stored in /build/tasks

Some useful tasks

NOTE: Run all of these from the N1 root folder.

Linting:

`script/grunt lint`

Building:

`script/grunt build`

The build folder has its own package.json and is isolated so we can use npm to compile against v8's headers instead of apm