mirror of
https://github.com/Foundry376/Mailspring.git
synced 2025-02-23 15:46:28 +08:00
fd838a4280
Summary:
In client-app/node_modules Lerna symlinks isomorphic-core to '../../'.
When we copy everything over to our tmp directory when building, we copy
over the relative symlink! Damn you lerna.
We get around this by resolving the symlinks BEFORE copying and caching
them in the installer task. Then the file copy always works.
Also, for some reason the glob {absolute} param doesn't seem to work in
the latest version. I'm manually creating an absolute path for the compile
target since it's a bit more transparent what's happening anyway.
Test Plan: `npm run build-client`
Reviewers: spang, jerm, juan, halla
Reviewed By: juan, halla
Differential Revision: https://phab.nylas.com/D3988
|
||
|---|---|---|
| .. | ||
| config | ||
| docs_templates | ||
| resources | ||
| tasks | ||
| Gruntfile.js | ||
| local-ci.sh | ||
| 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