I played around with this for our React Native codebase but ended up going with ESLint (https://eslint.org/) and customizing the rules there. I like that ESLint will combine simple linting with code style in a non-automatic way.
Report
Using on all frontend projects. Saves our teams time by never having to discuss formatting again.
Pros:
Never think about formatting JavaScript/TypeScript/JSX/CSS/GraphQL/Markdown/... again.
Has good support in editors, IDE''s and command-line.
Cons:
Could extend support to more styling/markup/programming languages ;)
Report
Everyone on the team can be on the same page about style and focus more on good quality engineering instead of styling nitpicks. Prettier works, is fast, and is extensible. It also supports other languages and file types such as TypeScript, .graphql files, CSS, and more.
Prettier has been invaluable in helping me keep code clean and consistent. It's an awesome tool to keep your code pretty, with it's very little space for customization it's the gofmt for the JavaScript world (but it's not limited to JS). It's a great tool to use alongside ESLint for error checking and more static analysis. I wrote about my usage of Prettier on my blog https://flaviocopes.com/prettier/ recently, I really enjoy having Prettier drive more productivity as I focus on the functionality of my code rather than on the style.
Report
Most likely the most influential project of 2017
Pros:
Achieves deterministic and robust code formatting via strong enforcement of code style opinions. A must for any JS team, small or big.
Cons:
Actually nothing.
Report
It's awesome tool which should be used in every company doing JS/TS to speed up development, and remove need to care much about code style - which will be great by automated format.
Pros:
Remove need to manually format code again. Great to end code style wars in company.
Cons:
Not everyone might initially like all formatting rules.
Report
I believe it's must have for any projects (that can be formatted by this tool). The best way is configuring auto formatting by using husky + lint-staged + prettier tools.
Pros:
No worries about how code looks. Easily reviewing PRs, you see only meaningful changes.
Replies
Create Node CLI
ntwrk
Using on all frontend projects. Saves our teams time by never having to discuss formatting again.
Pros:Never think about formatting JavaScript/TypeScript/JSX/CSS/GraphQL/Markdown/... again.
Has good support in editors, IDE''s and command-line.
Cons:Could extend support to more styling/markup/programming languages ;)
Everyone on the team can be on the same page about style and focus more on good quality engineering instead of styling nitpicks. Prettier works, is fast, and is extensible. It also supports other languages and file types such as TypeScript, .graphql files, CSS, and more.
Pros:Simplifies life. No longer worry about formatting
Cons:None
The Valley of Code
Most likely the most influential project of 2017
Pros:Achieves deterministic and robust code formatting via strong enforcement of code style opinions. A must for any JS team, small or big.
Cons:Actually nothing.
It's awesome tool which should be used in every company doing JS/TS to speed up development, and remove need to care much about code style - which will be great by automated format.
Pros:Remove need to manually format code again. Great to end code style wars in company.
Cons:Not everyone might initially like all formatting rules.
I believe it's must have for any projects (that can be formatted by this tool). The best way is configuring auto formatting by using husky + lint-staged + prettier tools.
Pros:No worries about how code looks. Easily reviewing PRs, you see only meaningful changes.
Cons:Not found
Medium TOC