1. posts
  2.  → Prettier
  3.  → reviews
About

Prettier is an opinionated code formatter

Would you recommend this product?
Lead Digital Weaver

I'm not a Javascript developer so I love that Prettier makes generally good formatting decisions for me, freeing need up to think about the code. It's easy to apply Prettier to any project I'm working on, even if other proper in the project aren't using it.

Pros:

No configuration, easy to set up, defaults everyone can agree on

Cons:

Harder to tell that a project is using Prettier

Share
> Cons: Harder to tell that a project is using Prettier Most editors have a setting that enables format on save only if the project is using prettier (either by looking for a config file or the dependency in package.json). I find that very useful when working on multiple project that may or may not be using it.
CEO @ ContentKing
"defaults everyone can agree on" bold statement ;)
Google Dev Expert · Head of DevRel

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 tested

Cons:

Nothing for what it promises.

Share
Hi, I'm Tim

Changed the way I develop js apps forever

Pros:

Never think about formatting again

Cons:

Can't write code for you

Share
Creator of Blitz.js | CEO Flightcontrol

It’s truly an essential for modern developers.

Pros:

Turn my ugly code into a beauty!

Cons:

It’s not automatically built into every code editor

I write code and design stuff.

I love it ! here is a demo https://twitter.com/Sapragus/sta...

Pros:

Turns messy 3am w redbull code blocks into beauty

Cons:

None

Front-end Developer

I absolutely love Prettier. At first, I was off-put by the fact that configuration is a second-class citizen. I quickly realized that's the whole point.

Pros:

Allows me to focus on the code instead of how it looks. 🙌

Cons:

No built-in PHP support

Software Engineer

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

CTO of Bae Mingo

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.

Frontend developer, freelancer.

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

CTO, Qiban

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.

This should be called Code Nazi - it's opinionated nature (good term for it - opinionated is not a good thing) makes it useless in my books. It should allow each user to customize EVERY aspect of their environment. That way, the debate about, for example, whether to use spaces or tabs (an age old debate) simply goes away. Each programmer gets the file out of the repository, it's formatted to their liking and when they check it back in it gets formatted to a standard specification determined BY THE ORGANIZATION, NOT Code Nazi.
PS: There's nothing "pretty" about their format.