README.md
# Strict Standard
[](https://travis-ci.org/denis-sokolov/strict-standard)
[](https://codeclimate.com/github/denis-sokolov/strict-standard)
[](https://gemnasium.com/denis-sokolov/strict-standard)
[](https://www.codacy.com/app/denis-sokolov/strict-standard)
[](https://www.bithound.io/github/denis-sokolov/strict-standard)
[](https://github.com/denis-sokolov/strict-standard)
[](https://github.com/feross/standard)
The [standard JavaScript code style by feross](https://github.com/feross/standard) is a great step to standardize the look and feel of JavaScript source files. Strict Standard uses that and adds on top of it the amazing capabilities of ESLint to detect actual errors in your code. There are **no style differences** from the main standard, only **more error catching**.
As new heuristics for catching errors are added to ESLint, they will be added to Strict Standard bumping the major number accordingly. If you use Strict Standard, you can be sure, that all the best tools to catch errors in your code are all being applied to your code.
## Usage
```
npm install --save-dev strict-standard
```
Add the following to your `package.json`:
```
{
"scripts": {
"lint": "strict-standard"
}
}
```
Alternatively, use [an eslint config](https://github.com/denis-sokolov/strict-standard-config) directly. That allows contributors who have eslint integrated in their editors get the correct errors without any setup.
## Badge
[](https://github.com/denis-sokolov/strict-standard)
```markdown
[](https://github.com/denis-sokolov/strict-standard)
```