Everything awesome for using npm as a build tool.
You might also like awesome-npm.
Notice: I'm currently too busy to actively expand this list; therefore, I've decided to make this an OPEN Open Source Project. Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit.
Blog post by Keith Cirkel.
Sequel to »Why we should stop using Grunt & Gulp«.
Article by Cory House.
Blog post by Michael Kühnel covering advanced topics.
The most comprehensive guide to using npm Scripts by Dr. Axel Rauschmayer.
Talk at Nordic.js 2015 by Kate Hudson.
Video tutorial series on setting up a front-end build system.
Simple task runner with a terse syntax.
Fully featured task runner.
Expand scripts from package.json to improve execution speed.
Tools for running multiple commands or npm scripts in parallel or sequentially.
Tools to watch your source files and run a build command whenever any of the files change.
Simple zero-configuration command-line http server.
Simple development http server with live reload capability.
Delete files or directories; like `rm -rf`.
Safer file and folder deletion.
Create a directory, creating parent directories if needed; like `mkdir -p`.
`cp -r` for Node.js.
File/directory copying/renaming.
Copy a list of files into a directory.
`rsync`-like directory syncing with watch mode.
Cross-platform `echo` with JS escape sequence support.
Clear the terminal.
Set environment variables for scripts, unix-style.
Run platform-specific npm scripts.
Utility that reads from standard input and writes to standard output and files; like Unix `tee`.
Print a file to stdout, with optional watch mode; sorta like Unix `cat`.
Utilities to perform common command-line tasks without worrying about cross-platform compatibility.
Collection of common Unix utilities implemented in Node.js; example usage: `shx rm somefile`.
Take contents of a file and output as new file with a hash in the name.
Get the gzipped size of a file or stdin.
Open websites, files, executables, etc. with the user's preferred application.
Add header / banner info to a file.
Get main bower files on the command line.
Send native desktop notifications when npm scripts fail.
The npm scripts GUI.
npm scripts desktop client.
Run locally-installed node module executables. Useful for debugging npm scripts.
Quickly run npm scripts by prefix without typing the full name.
Edit npm scripts from the command line without worrying about JSON escaping.
Interactive cli menu to list and run npm scripts.
A quick reference of the shell operators & commands that work the same on Unix and Windows.
&& to run commands in sequence. If a command fails, the script exits.| to pipe the stdout of one command into the stdin of the next. (do-something | something else)> to write the stdout of a command to a file. (do-something > file)< to send the contents of a file to a command's stdin. (command < file)cd <dir> to change the current working directory to <dir>. Note that cd alone prints the current working directory on windows, but changes the working directory to ~ on *nix.You can use npm run-script or npm run; they both do the same thing, but npm run is shorter.
npm run to print a list of scripts.npm run script (where script is the name of your script) will run prescript, script, and postscript; in that order.
pre and post hooks (i.e. preprescript won't work).-- to npm run, followed by the arguments. Example: Given the script "mocha": "mocha", you can run npm run mocha -- --reporter xunit. This effectively runs mocha --reporter xunit.npm test is the same as running npm run test. The same applies to npm start and npm stop.npm run <script> -s to silence the default npm output (useful for calling a script within another script).