semistandard

even though StandardJS's decisions don't match the style predominant in the JS community I find it particularly ironic that there's a reasonably popular fork called semistandard. [1] In all seriousness though, I'd really love to see the JS community move towards tools like prettier[2] instead of continuously trying to establish "one eslint config to rule them all". I just want each repo I work with to configure my editor for me and reformat stuff automatically (a la gofmt) so I can forget about it. Even if some of the particular style decisions are ones that I personally don't agree with, it doesn't matter — the value of having those decisions abstracted away from me in the first place is significant enough that any minor quibbles fade away pretty quickly. Then I can focus on writing and reading code, not on arguing about whether we shoul

Personally, no semi colons is a deal breaker for me. It's like a period at the end of the sentence that means, "That's the entire statement". So, it's neat in the config-less way, but I won't be using it. (there is a semicolon version by the way https://github.com/Flet/semistandard )

https://github.com/Flet/semistandard Of course the solution is to create a separate "standard."

For Javascript: - https://github.com/feross/standard - https://github.com/Flet/semistandard Node: Both of these include a style-enforcement tool that can be scripted via NPM scripts. For CSS: http://semantic-ui.com/usage/theming.html Note: Semantic-UI is a lot like Bootstrap in that it provides a lot of useful visual classes/components. In addition, it can be extended to use custom themes.

It's one less thing to think about. Anyway, for JavaScript there's the standard[1] and semistandard[2] projects. They are different from other style guides because they're standalone applications that would fail your tests if your files do not adhere to the standard (if set up correctly). Think of them as unconfigurable linters. [1] https://github.com/feross/standard [2] https://github.com/Flet/semistandard

ESLint is nice but it's a pain to setup. A lot of people are beginning to use standard linters built on top of it like `semistandard` [0] . [0] https://github.com/Flet/semistandard

I'm using standard [1] for style. I love semicolons too, but am giving it a go without them here. TBH, it feels kinda weird, and I'll probably end up on semi-standard [2] in the end. [1] https://github.com/feross/standard [2] https://github.com/Flet/semistandard

>Unfortunately the rules are complex, prone to certain errors, and I can't rely on everyone I ever work with understanding all of those rules. Are they really complex? This recently released version 4.0.0 of the JavaScript Standard Style [1] suggests to never start a line with "(" or "[". This rule looks even simpler than the rules of operator precedence. [1] https://github.com/feross/standard Update: Now I learned about the JavaScript Semi-Standard Style [2] which accually enforces semi-colons. Quite hilarious. [2] https://github.com/Flet/semistandard