NPM Packages and Styles

Java Script "Standard" Style [click]

One JavaScript Style to Rule Them All

No decisions to make. No .eslintrc, .jshintrc, or .jscsrc files to manage. It just works.

This module saves you (and others!) time in two ways:

• No configuration. The easiest way to enforce consistent style in your project. Just drop it in.
• Catch style errors before they're submitted in PRs. Saves precious code review time by eliminating back-and-forth between maintainer and contributor.

# **mocha standard** [ [click] ](https://www.npmjs.com/package/mocha-standard) Integrates standard into your mocha tests. This allows you to enforce a "one true" JavaScript coding style in your project via Mocha tests.

This offers a finer alternative to adding standard into package.json's scripts.test block.

• Runs in the same node process as mocha, removing maybe 500ms of startup time.
• Use mocha --watch to recheck for style failures. standard is used programatically, removing a huge overhead (around 1500ms) in re-running it repeatedly with --watch.
• Painlessly integrate standard into your travisci.org tests.

# **nodemon** [ [click] ](https://www.npmjs.com/package/nodemon) For use during development of a node.js based application.

nodemon will watch the files in the directory in which nodemon was started, and if any files change, nodemon will automatically restart your node application.

nodemon does not require any changes to your code or method of development. nodemon simply wraps your node application and keeps an eye on any files that have changed. Remember that nodemon is a replacement wrapper for node, think of it as replacing the word "node" on the command line when you run your script.

# **Travis CI** [ [click] ](https://travis-ci.org/) Easily sync your GitHub projects with Travis CI and you’ll be testing your code in minutes!