All the goodness of [standard/standard] with Webkollektivet's preferences sprinkled on top.
npm install w12t-standard
- Multiline comma dangle
- JSX double quotes
- Check [standard/standard] for the rest of the rules.
npm install w12t-standard -g
After you've done that you should be able to use the
w12t-standard program. The simplest use
- Atom users - Install linter-js-standard-engine
Specify what linter to use using by setting standard-engine in your package.json file:
What you might do if you're clever
- Add it to
- Check style automatically when you run
$ npm test Error: Code style check failed: lib/torrent.js:950:11: Expected '===' and instead saw '=='.
- Never give style feedback on a pull request again!
To use a custom parser, install it from npm (example:
npm install babel-eslint) and add this to your package.json:
Just like in
standard, The paths
coverage/**, hidden files/folders
.), and all patterns in a project's root
.gitignore file are
automatically excluded when looking for
.js files to check.
Sometimes you need to ignore additional folders or specific minfied files. To do that, add
w12t-standard.ignore property to
Make it look
If you want prettier output, just install the
snazzy package and pipe
w12t-standard to it:
$ w12t-standard --verbose | snazzy
See [standard/standard] for more information.