LinthelmIntroductions to linters, static analysis and code-quality tools

Formatters

What is dprint? An introduction to the code formatting platform

By the Linthelm editorial team · Published · Updated

dprint is a pluggable and configurable code formatting platform written in Rust. It is a command line application that automatically formats code, and it aims to be a single formatting tool for every language in a repository. Formatting for each language is handled by plugins that the CLI loads.

Tool
dprint
Made by
dprint
Official site
dprint.dev
Category
Formatters

Who makes dprint

dprint is made by the dprint project, which publishes the CLI and the official plugins. The official website is linked below, and it is the place to look for current documentation and the list of plugins.

The project describes itself as a formatting platform rather than a single-language formatter. That framing explains most of its design: the core tool is a runner, and the language support comes from plugins.

Official website: dprint.dev

What dprint is for

dprint is for formatting source code and related files automatically, so that style is applied by a tool instead of being debated in review. Its stated aim is to be one formatting tool for every language in a repository, which means a project does not need a separate formatter command for each file type.

It is built with Rust and WebAssembly and uses incremental caching by default. The CLI is distributed as a single static binary with no runtime dependencies, so it can be installed without first setting up a language runtime.

dprint check verifies that code is already formatted. That gives you a way to confirm formatting without relying on the formatting command itself.

Who dprint is for

The vendor names teams as the audience. The features that matter most to a team are the ones that make formatting consistent and reproducible: plugin options that match a house style, plugins that are pinned and versioned in configuration, and one tool that covers the languages in a repository.

Teams that already rely on other formatters are also addressed. Wrapper plugins and an Exec plugin let dprint sit in front of existing tools instead of replacing them all at once.

Notable capabilities

dprint combines a plugin system with a small, dependency-free CLI. The capabilities below come from the verified feature set.

  • Official plugins cover TypeScript/JavaScript, JSON, Markdown, TOML, Dockerfile, SQL and Jupyter notebooks.
  • Official plugins expose configuration options, so formatting can match a team's house style.
  • Wasm plugins run sandboxed, without network or file system access.
  • Plugins can be loaded from a URL or file path, and pinned and versioned in config.
  • Community plugins can be mixed with official formatters.
  • Wrapper plugins integrate existing formatters such as Prettier, Biome and Oxc, and an Exec plugin can wrap any other CLI formatter.
  • dprint init scaffolds a dprint.json configuration file in the project, and plugins can be added to the config from the command line.
  • The CLI installs via shell script, PowerShell, npm, Homebrew or Cargo.

How dprint fits formatters

Formatters rewrite code to a consistent layout without changing what it does. dprint belongs in this category as a multi-language platform: instead of one tool per language, it hosts formatters as plugins behind one CLI and one configuration file.

Its plugin model is what separates the platform from a single formatter. Because it can wrap tools such as Prettier, Biome and Oxc, and can run any other CLI formatter through the Exec plugin, it can act as a common entry point for formatters that already exist.

For Linthelm's wider niche of linters, static analysis and code quality, formatters cover the layout side of consistency. They are usually used alongside linters and analyzers, which look for problems in the code itself. dprint check fits that workflow as a verification step that confirms code is already formatted.

Frequently asked questions

What is dprint used for?

dprint is used to automatically format code across many languages through one CLI. It aims to be a single formatting tool for every language in a repository.

What is dprint written in?

dprint is written in Rust and built with Rust and WebAssembly. Its plugins are Wasm plugins that run sandboxed, without network or file system access.

Which languages does dprint support?

Official plugins cover TypeScript/JavaScript, JSON, Markdown, TOML, Dockerfile, SQL and Jupyter notebooks. Community plugins, wrapper plugins and an Exec plugin extend that further.

How do I check that code is formatted with dprint?

Run dprint check, which verifies that code is already formatted. To get started, dprint init scaffolds a dprint.json configuration file in the project.

How do I install dprint?

It can be installed via shell script, PowerShell, npm, Homebrew or Cargo. The CLI is a single static binary with no runtime dependencies.

Sources. This introduction is based on the vendor's official pages, checked on 21 November 2026 (Asia/Dhaka):

Linthelm is independent and is not affiliated with dprint. Product names belong to their owners. Features change; confirm details on the official website.