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.
npm run ReferenceTools 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.
Utilities to perform common command-line tasks without worrying about cross-platform compatibility.
rm -rf.mkdir -p.cp -r for Node.js.rsync-like directory syncing with watch mode.echo with JS escape sequence support.tee.cat.shx rm somefile.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.npm run ReferenceYou 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).See CONTRIBUTING.md.