Prettier

Prettier
Name	Prettier

Prettier is an opinionated code formatter for multiple programming languages and syntaxes. It enforces a consistent code style by parsing source files and reprinting them with a fixed set of formatting rules, aiming to reduce debates about code layout and minimize manual formatting effort. The tool is widely adopted in open-source projects and commercial codebases alongside editors and continuous integration systems.

History

The project emerged from discussions in the JavaScript community and was influenced by formatting tools and projects such as Guido van Rossum-era innovations, GNU Emacs-adjacent tooling, and ideas from the Rust formatter movement. Early development was driven by contributors with experience from organizations like Facebook, Google, and Microsoft, and it grew rapidly through exposure on platforms such as GitHub, Stack Overflow, and Hacker News. Adoption accelerated as package managers and ecosystems including npm, Yarn, and pnpm integrated it into workflows, while continuous integration services like Travis CI, CircleCI, and GitHub Actions provided automation paths. Over time the project expanded language support and forged collaborations with tooling projects connected to TypeScript, Babel, and ESLint communities.

Features

Prettier provides deterministic formatting by parsing source code into an abstract syntax tree (AST) and reprinting it, a technique shared with tools in the lineage of Clang's formatting utilities and language-specific formatters such as gofmt and the Rustfmt project. Supported syntaxes include dialects and ecosystems tied to JavaScript, TypeScript, CSS, HTML, JSON, and template systems used in frameworks like React and Vue.js. The formatter implements print width, indentation, trailing comma policies, and semicolon handling, comparable to style decisions discussed in the context of Airbnb JavaScript Style Guide and Google JavaScript Style Guide debates. It offers options for handling embedded languages in files associated with Markdown, GraphQL, and YAML, and it integrates with parsers and transpilers such as Babel, Esprima, and Acorn. Performance characteristics and stability are influenced by testing practices similar to those used by JUnit-driven projects and by continuous integration examples from CircleCI and Travis CI.

Usage

Developers invoke the formatter via command-line interfaces provided through ecosystem package managers like npm and Yarn, and by integrating it into repository workflows managed with Git, Mercurial, or Subversion. It is commonly added to pre-commit or pre-push hooks using helpers in the style of Husky or coordinated with linting tools such as ESLint and type checkers like TypeScript to create combined verification pipelines similar to setups found at organizations like Airbnb, Uber, and Netflix. Teams use it in combination with code review platforms such as GitHub, GitLab, and Bitbucket to ensure diffs reflect only semantic changes. Automation in continuous delivery environments leverages Jenkins, GitHub Actions, and CircleCI to run formatting checks on pull requests.

Configuration

Configuration is typically managed via project-level files and package manifests familiar to maintainers using package.json in Node.js ecosystems, and via dedicated configuration files influenced by patterns from EditorConfig. Options include line width, indentation width, single-quote versus double-quote policies, and trailing comma styles, analogous to choices documented by style guides like Airbnb JavaScript Style Guide and StandardJS. Integration with monorepo tools such as Lerna and Nx enables centralized configuration across packages, while overrides allow per-file or per-directory exceptions similar to patterns used with ESLint configuration cascading. Teams enforce configuration via CI checks and repository policies enforced in platforms like GitHub Enterprise and GitLab.

Integrations and editor support

The formatter has broad editor support through extensions and plugins for Visual Studio Code, Sublime Text, Atom, Vim, Neovim, and Emacs. Editor integrations often surface configuration through settings panels familiar to users of Visual Studio Code and provide on-save formatting hooks akin to features in IntelliJ IDEA and WebStorm. Language server integrations align with the Language Server Protocol ecosystem used by Microsoft and others, and plugin ecosystems for build tools like Webpack, Rollup, and Parcel offer task-oriented integrations. Formatting is also implemented in CI runners, pre-commit frameworks like pre-commit, and code hosting integrations for GitHub and GitLab that present diffs and suggestions to reviewers.

Development and governance

Development occurs in public repositories and follows open-source contribution models comparable to projects hosted on GitHub and governed by community-maintained contribution guidelines similar to those used by Linux kernel-adjacent projects. Contributors include individuals associated with Facebook, Microsoft, Google, and independent maintainers, and collaboration follows practices adopted in ecosystems around Node.js, TypeScript, and Babel. Release management and semantic versioning practices echo strategies used by major libraries such as React and Angular, while issue tracking and roadmap discussions take place on platforms like GitHub issues and community forums modeled after Stack Overflow and Discourse. Community governance combines core maintainers, corporate contributors, and a broad base of external collaborators.

Category:Software