Course contentsShow
← JavaScript
Lesson 2584 of 2,72352. Linting and FormattingFree lesson

The Philosophy of Opinionated Formatting

Embrace Prettier's limited configurability to eliminate style debates and focus on logic.

The Philosophy of Opinionated Formatting

You'll learn why Prettier intentionally limits your configuration choices and how this design decision benefits your team.

The Counterintuitive Advantage of Fewer Options

Most tools pride themselves on flexibility. Prettier does the opposite—it deliberately offers minimal configurability. You can adjust a handful of settings (print width, tabs vs spaces, semicolons, quotes), but that's essentially it. You cannot fine-tune every stylistic preference.

This feels restrictive at first. But here's the philosophy: style debates are a waste of developer time.

Think of it like electrical outlets in your country. Everyone uses the same standard plug shape—not because it's objectively "better" than alternatives, but because having a standard is what matters. Prettier works the same way. By removing 90% of formatting choices, it eliminates 100% of formatting arguments.

Focus Energy Where It Counts

When Prettier formats your code automatically with limited options, two things happen:

  1. Code reviews focus on logic, not whether someone put a brace on the wrong line
  2. Onboarding is faster because there's no "house style guide" to memorize—Prettier is the style

The tool's creator could have added hundreds of configuration options. Instead, they chose to say "this is good enough" for most cases. The few options that exist (like print width) genuinely affect readability; the rest are arbitrary preferences that don't deserve debate time.

Embrace the Constraint

Prettier's philosophy asks you to surrender control over minutiae in exchange for cognitive freedom. You might not love every formatting decision, but you'll love never arguing about formatting again.

Key Takeaway: Prettier's limited configurability isn't a weakness—it's a feature that eliminates bikeshedding and lets your team focus on building software, not debating style preferences.