Prettier is an opinionated code formatter
No configuration, easy to set up, defaults everyone can agree onCons:
Harder to tell that a project is using Prettier
Big fan of the Prettier project, the team behind it, and how it has easier configuration. Wish there could be WordPress support (CIP → https://ahmda.ws/2EPreSL)Pros:
Best printer of AST I've used in a long long time. Less configuration is a big plus as well. Huge community support behind it. Battle testedCons:
Nothing for what it promises.
Using on all frontend projects. Saves our teams time by never having to discuss formatting again.Pros:
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 formattingCons:
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:
As a frontend engineer, the code format is very very important to me. I used ESLint at first, and have to manually format every line of code. Later I found Prettier, it really save me lots of time. However, sometimes it will conflict with specific ESLint rules, in that case, you have to manually disable some ESLint rules in .eslintrc file in order to let Prettier handle everything.Pros:
Save time for formatting JS code.Cons:
Conflict with ESLint.