Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2025-02-23 23:54:13 +08:00
Code Issues Projects Releases Packages Wiki Activity
Mailspring/packages/client-app/build
History
Evan Morikawa a7686bb35b [client-app] build tasks now use absolute paths 
Summary:
Grunt is hardcoded to use paths relative to wherever the Gruntfile is
located. Unfortunately it also expects the grunt packages to be siblings
of that gruntfile. We can get around this by changing the relative base
path, but then the cwd is different for each tasks. This is okay as long
as we use absolute paths for various files in each of our tasks. This
updates our grunt tasks to use absolute paths

Test Plan: `npm run build-client`

Reviewers: spang, halla, jerm, juan

Reviewed By: juan

Differential Revision: https://phab.nylas.com/D3987
2017-02-21 14:35:51 -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] build tasks now use absolute paths 2017-02-21 14:35:51 -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

README.md

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