Are you trying to start a war? LOL The configurable options in prettier are there because they are too controversial for there to be one universally accepted standard. It's all personal opinion. More on reddit.com

Next themselves do: https://nextjs.org/docs/app/building-your-application/configuring/eslint More on reddit.com

Prettier is not very configurable by design, in order to remove the probability of teams arguing about what the configuration should be. The configurable options in your screenshot are pretty much all the options you have. Prettier is incredibly opinionated, and IMO some of their opinions are stupid. I still use it though -- because while I hate what Prettier does to my own code, I put up with it if it means my sloppy coworkers' code gets any sort of formatting at all before I have to deal with it. If that tradeoff is unacceptable, you might consider using eslint to handle formatting instead of Prettier. Edit: In your specific instance, there is a method to the madness however. Within a , white space is significant and will result in extra space characters in the rendered page. While the markup isn't as attractive, it is usually the right decision to not add space there just for the sake of tags lining up. More on reddit.com

I manage and use a monorepo for my ESLint configs via NPM - each package is a single config (for Vue, React, TypeScript) that extends a set of base settings that I use throughout all of my JS/TS code. I use This configuration has worked well for me on both personal and enterprise-scale projects and I've been able to enjoy consistent code style with minimal boilerplate and config. Whenever I need to override a rule for some project-specific need, I simply extend the config in the consuming project. For Prettier, I likewise pull in a shared config that I publish on NPM. Both ESLint and Prettier have first-class support for packaged, shared configs i.e. this is the recommended way to consume such configs across many projects. Prettier is very opinionated and far less configurable than ESLint by design. Don't confuse these tools, however. ESLint is a linter; Prettier is a formatter. The goal of Prettier is to offload the cognitive overhead involved with deciding on a formatting style. Because there's potential overlap between the two tools; use `eslint-config-prettier` when using the two together to prevent collisions between them. To answer your next question: I lint and format on save, and I use Git hooks installed by Husky and executed through Lint-Staged (this tool helps ensure your Git hooks only run on modified files, etc) to ensure there are no lint or formatting errors whenever making a commit or pushing code. This is helpful for teams, as some developers tend to forget to run lint tasks, or don't have the Prettier extension installed in their IDE. If there are lint errors, the commit is rejected until fixed. YMMV - you'll need to fine-tune the strictness of this based on the team's needs. To answer your "random question": preference for ubiquitous backticks is rare and non-idiomatic in JS/TS. Use backticks for multi-line strings or template literals (string interpolation - and in less common cases - tagged template functions ). For all other use-cases, use single or double-quote (it doesn't matter which, just be consistent about the choice you make). More on reddit.com