Mailspring/packages/client-app/build
Evan Morikawa 5024f9c2cc [client-app] also upload a next-version to S3 for autoupdate testing
Summary:
We never want to ship the last release we'll ever ship.
This can happen if the new version's autoupdater is broken.
To test this we upload to a version n+1 higher than the current one.

Test Plan: manual

Reviewers: juan, spang, halla

Reviewed By: halla

Differential Revision: https://phab.nylas.com/D4125
2017-03-07 14:54:50 -05: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] also upload a next-version to S3 for autoupdate testing 2017-03-07 14:54:50 -05:00
Gruntfile.js [client-app] build tasks now use absolute paths 2017-02-21 14:35:51 -05:00
local-ci.sh [client-*] Rename packages folders and update readme 2017-02-16 13:31:37 -08: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