Bun ships with a fast, built-in code formatter. There's nothing to install and nothing to configure.

• JavaScript, TypeScript, JSX, CSS, SCSS, Less, HTML, Vue, Svelte, Angular, JSON, YAML, TOML, Markdown, MDX, GraphQL, and Handlebars
• The same output as Prettier
• Sorts imports, Tailwind CSS classes, and package.json
• Works with your existing Prettier or oxfmt config

Run the formatter

bun fmt

src/index.ts
src/server.ts
Formatted 2 files, 2 unchanged [3.47ms]

bun fmt rewrites the files in the current directory that need it and prints their names. It skips node_modules, anything in your .gitignore or .git/info/exclude, minified files (*.min.js, *.min.css) and lock files such as package-lock.json.

To format specific files, pass paths or globs.

bun fmt src "test/**/*.ts"

Embedded code is formatted too: <script> and <style> in HTML, Vue, and Svelte, code blocks in Markdown, and css`...`, html`...`, and graphql`...` templates in JavaScript.

A syntax error inside a <script> or <style> of a Svelte component is a warning. That block stays as written, and the rest of the file is formatted.

Check without writing

--check lists the files that need formatting and writes nothing.

bun fmt --check

src/index.ts
src/server.ts
2 files need formatting. Run bun fmt to fix them.

The exit code is 1 if a file needs formatting, 0 if none do, and 2 if something went wrong, like a syntax error. That makes it the command for CI.

steps:
  - uses: actions/checkout@v4
  - uses: oven-sh/setup-bun@v2
  - run: bun fmt --check

Options

Options live in bunfig.toml. To create the section, run bun fmt --init.

[fmt]
printWidth = 100
semi = false
singleQuote = true

All of Prettier's options work, under the same names. Each one is also a flag, like --print-width 100 or --no-semi.

Different options for some files

[[fmt.overrides]]
files = ["*.test.ts", "scripts/**"]
options = { printWidth = 120 }

.editorconfig

bun fmt reads indent_style, indent_size, tab_width, max_line_length, and end_of_line from .editorconfig. bunfig.toml overrides them.

Ignore files

Every .gitignore in the repository counts, whichever directory you run bun fmt from. Outside a repository, those in the current directory and below it count. With a Prettier config, only the .gitignore in the current directory does, because that's the only one Prettier reads.

To skip more than .gitignore does, list the files in bunfig.toml. A .prettierignore file works too.

[fmt]
ignorePatterns = ["vendor/", "**/*.gen.ts"]

Ignore code

bun fmt uses Prettier's comment, so existing ones keep working. It applies to the next statement, element, or rule.

// prettier-ignore
const matrix = [
  1, 0, 0,
  0, 1, 0,
  0, 0, 1,
];

In JSX it's {/* prettier-ignore */}, in CSS /* prettier-ignore */, in HTML and Markdown <!-- prettier-ignore -->, and in YAML and GraphQL # prettier-ignore.

Sort imports

[fmt]
sortImports = true

import { z } from "zod";
import { b, a } from "./util";
import { db } from "@/db";
import { readFile } from "node:fs/promises";
import { c } from "./util";

import { readFile } from "node:fs/promises";

import { z } from "zod";

import { db } from "@/db";

import { a, b, c } from "./util";

• Imports are grouped: built-in modules, packages, aliases like @/, relative paths, styles.
• Each group is sorted by path, and the names in { } are sorted too.
• Two imports from the same module become one.
• Side-effect imports like import "./setup" never move, and nothing moves past one.
• A comment directly above an import moves with it. Above the first import, comments about the whole file stay at the top: // @ts-nocheck, /// <reference ... />, /* eslint-disable */, // @flow, /** @jsxImportSource ... */, a license.

To pick your own groups, use a table. See format.sortImports.

[fmt.sortImports]
groups = ["react", "builtin", "external", "internal", ["parent", "sibling", "index"]]
customGroups = [{ groupName = "react", elementNamePattern = ["react", "react-dom/**"] }]

Sort Tailwind CSS classes

[fmt]
sortTailwindcss = true

<a className="p-4 flex m-2" /> // [!code --]
<a className="m-2 flex p-4" /> // [!code ++]

Classes are sorted in Tailwind's recommended order, in class and className and in calls to clsx, cn, cva, twMerge, and a few more. They are sorted with your project's tailwindcss, version 3 or 4, and are left as they are if it isn't installed.

If your .prettierrc lists prettier-plugin-tailwindcss, sorting is already on, with that plugin's options and defaults.

To name your own functions or your stylesheet, use a table.

[fmt.sortTailwindcss]
stylesheet = "./src/app.css"
functions = ["clsx", "tw"]

Sort package.json

[fmt]
sortPackageJson = true

Keys go in the conventional order: name, version, description, and so on.

If your .prettierrc lists prettier-plugin-packagejson, sorting is already on and uses that plugin's order.

{
  "dependencies": { "zod": "^4.0.0" },
  "scripts": { "dev": "bun --hot src/index.ts" },
  "version": "1.0.0",
  "name": "app"
}

{
  "name": "app",
  "version": "1.0.0",
  "scripts": {
    "dev": "bun --hot src/index.ts"
  },
  "dependencies": {
    "zod": "^4.0.0"
  }
}

Format JSDoc comments

[fmt]
jsdoc = true

/**
 * adds two numbers
 * @returns {number} the sum
 * @param {number} b second number
 * @param {number} a   first number
 */

/**
 * Adds two numbers
 *
 * @param {number} a First number
 * @param {number} b Second number
 * @returns {number} The sum
 */

Svelte

.svelte files are formatted by default, like prettier-plugin-svelte formats them. To change how, use a table. These are the defaults:

[fmt.svelte]
sortOrder = "options-scripts-markup-styles"
allowShorthand = true
indentScriptAndStyle = true

To leave .svelte files alone, turn it off.

[fmt]
svelte = false

See format.svelte.

Standard input

Pipe text through bun fmt. It prints the result and writes nothing. The path picks the language and the options. The file doesn't have to exist.

bun fmt --stdin-filepath src/index.ts < src/index.ts

No path to give? Name the parser instead. Your config still applies, except for what goes by a file name: overrides, .editorconfig, and ignore files.

bun run generate-types | bun fmt --parser typescript > types.ts

Git hooks

--staged formats only the files you're about to commit and stages them again, so you don't need lint-staged.

#!/bin/sh
bun fmt --staged

If a file has both staged and unstaged changes, Bun looks at the staged version, which is what the commit gets. It doesn't write such a file, because staging it again would commit the rest. If the staged version needs formatting, Bun names the file and exits with code 2.

Config files, such as bunfig.toml and .prettierrc, are read from disk.

--changed formats the files that differ from your default branch. Pass a ref to compare with something else.

bun fmt --changed
bun fmt --changed=origin/dev

Migrate from Prettier or oxfmt

Already have a .prettierrc or an .oxfmtrc.json? bun fmt reads it and prints what that tool prints. Change the script and you're done.

{
  "scripts": {
    "format": "prettier --write .", // [!code --]
    "format": "bun fmt" // [!code ++]
  }
}

If package.json has a fmt script, bun fmt runs that script. Inside the script, bun fmt is the formatter. If package.json has "fmt" in it but can't be parsed, as in the middle of a merge, bun fmt can't tell whether that is a script: it formats nothing and exits with code 2.

Writing a tool that calls Bun in projects you don't control? Pass --no-script: bun fmt --no-script is always the formatter.

Astro isn't built in. If your .prettierrc lists its plugin, Bun sends those files to your installed Prettier. To see which files those are, and which packages you can uninstall:

bun fmt --doctor

See the guides: Migrate from Prettier and Migrate from oxfmt.

CLI Usage

bun fmt [flags] [files, directories, or globs]

Modes

Files

Options

All of Prettier's options are flags too.

Output

bun fmt also accepts the flags of Prettier and oxfmt. Run bun fmt --help --all to see them.