-
Should I put a eslintrc.json in my project?
https://github.com/Flet/semistandard/blob/master/eslintrc.json
-
In this issue we should discuss how we are going to handle code style.
This is not for a discussion of "spaces vs tabs" or "semicolon or not", this assumes that the value on code style lies in the co…
-
Based on a conversation internally, should we look to move to eslint instead of semistandard?
cc/ @anandthakker
-
https://github.com/Flet/semistandard/
-
- [x] MIT license
- [x] Move repository to `nowsecure` and drop the /private/ bit
- [x] lint semistandard warnings https://github.com/viaforensics/node-applesign/issues/4
- [x] publish to npm
-
```
± semistandard index.js | grep -v "indentation\|Unexpected\|space"
semistandard: Semicolons For All! (https://github.com/Flet/semistandard)
/Users/user/work/node-codesign/index.js:27:26: Expecte…
-
jslint is no longer the only option out there in terms of enforcing a style guide. The only requirement is that it must have a command line runner which can accept multiple files. Options are:
- [jscs…
-
[Standard](https://github.com/feross/standard) is built atop [eslint](https://github.com/eslint/eslint) and offers a set of default (unchangeable) eslint configuration rules and pre-commit linting. Wh…
-
See https://github.com/Flet/semistandard/ for reference.
We need to rebase and use the latest standard-engine and eslint plugins.
-
The maintainer of JShint has decided to take it in a direction where it focuses on and do not implement coding style, see this [SO answer](http://stackoverflow.com/questions/23097316/how-can-i-make-js…