Atom Build package

Automatically build your project inside your new favorite editor, Atom.

• cmd-alt-b / ctrl-alt-b builds your project.
• cmd-alt-g / ctrl-alt-g cycles through causes of build error. See Error Matching.
• cmd-alt-h / ctrl-alt-h goes to the first build error. See Error Matching.
• escape terminates build / closes the build window.

Supported build tools:

1. Custom by specifying your own build command
2. NodeJS (runs npm install) - if package.json exists where engines['node'] is set
3. Atom (runs apm install) - if package.json exists where engines['atom'] is set
4. Grunt - if Gruntfile.js exists
5. Gulp - if gulpfile.js exists
6. GNU Make - if Makefile exists
7. Elixir - if mix.exs exists
8. Cargo - if Cargo.toml exists * Supports error matching.

If multiple viable build options are found, atom-build will prioritise according to the list above. For instance, if package.json and Gruntfile.js are both available in the root folder, npm install will be executed by atom-build.

If you need to run grunt, gulp or other tool to build you project, then you can utilize the postinstall-script of package.json. This will also help you if grunt is run as a node module since it will be downloaded (via npm install) prior.

Specifying a custom build command

If the built-in defaults are not enough to suit your needs, you can specify exactly what to execute. Create a file named .atom-build.json in your project root:

{
  "cmd": "<command to execute>",
  "args": [ "<argument1>", "<argument2>", ... ],
  "sh": true,
  "cwd": "<current working directory for `cmd`>",
  "env": {
    "VARIABLE1": "VALUE1",
    "VARIABLE2": "VALUE2",
    ...
  },
  "errorMatch": "^regexp$"
}

Note that if sh is false cmd must only be the executable - no arguments here. If the executable is not in your path, either fully qualify it or specify the path in you environment (e.g. by setting the PATH var appropriately on UNIX-like systems).

Configuration options

• cmd - [required] The executable command
• args - [optional] An array of arguments for the command
• sh - [optional] If true, the combined command and arguments will be passed to /bin/sh. Default true.
• cwd - [optional] The working directory for the command. E.g. what . resolves to.
• env - [optional] An array of environment variables and their values to set
• errorMatch - [optional] A regular expression to match output to a file, row and col. See Error matching for details.

Replacements

The following parameters will be replaced in cmd, any entry in args, cwd and values of env. They should all be enclosed in curly brackets {}

• {FILE_ACTIVE} - Full path to the currently active file in Atom. E.g. /home/noseglid/github/atom-build/lib/build.js
• {FILE_ACTIVE_PATH} - Full path to the folder where the currently active file is. E.g. /home/noseglid/github/atom-build/lib
• {FILE_ACTIVE_NAME} - Full name and extension of active file. E.g., build.js
• {FILE_ACTIVE_NAME_BASE} - Name of active file WITHOUT extension. E.g., build
• {PROJECT_PATH} - Full path to the root of the project. This is normally the path Atom has as root. E.g /home/noseglid/github/atom-build
• {REPO_BRANCH_SHORT} - Short name of the current active branch (if project is backed by git). E.g master or v0.9.1.

Error matching

Error matching let's you specify a regular expression which captures the output of your build command and opens the correct file, row and column of the error. For instance:

a.c:4:26: error: expected ';' after expression
  printf("hello world\n")
                         ^
                         ;
1 error generated.

Would be matched with the regular expression: ^(?<file>[^\\.]+.c):(?<line>\\d+):(?<col>\\d+). After the build has failed, pressing cmd-alt-g (OS X) or ctrl-alt-g (Linux/Windows), a.c would be opened and the cursor would be placed at row 4, column 26.

Note the syntax for match groups. This is from the XRegExp package and has the syntax for named groups: (?<name> RE ) where name would be the name of the group matched by the regular expression RE.

The following named groups can be matched from the output:

• file - [required] the file to open. (?<file> RE).
• line - [optional] the line the error resides on. (?<line> RE).
• col - [optional] the column the error resides on. (?<col> RE).

Since the regular expression is written in a JSON file, backslashes must be escaped.

If your build outputs multiple errors, all will be matched. Press cmd-alt-g (OS X) or ctrl-alt-g (Linux/Windows) to cycle through the errors (in the order they appear in the output of the build script).

Often, the first error is the most interesting since other errors tend to be secondary faults caused by that first one. To jump to the first error you can use cmd-alt-h (OS X) or ctrl-alt-h (Linux/Windows) at any point to go to the first error.