You can find the sample project with different Prettier settings configured per-subfolder at bahmutov/prettier-config-example.
- Why Prettier?
- VSCode setup
- Format files from CLI
- Format staged files on commit
- Catch mis-formatted files on CI
- Common problems
- Use Eslint with Prettier
You can use Prettier from command line, or from your code editor whenever you paste or save a file. I prefer to use two solutions described in this blog post:
- format the file from VSCode every time I save it
- format the changed files on Git commit before committing them
Let me show you how to do both.
When setting up Prettier it is important to configure it per-project. Not every project uses the same code style, thus it is important to respect the style of whatever project you are currently working in. The demo repo bahmutov/prettier-config-example has two subfolders, each with its distinct code style, enforced by Prettier. In reality, each of your repos will have its style; I am using subfolders in order to keep the example simple.
I assume you are using NPM and have
package.json file inside the repository. Install Prettier
npm install --save-dev --save-exact prettier
At the root of the project create the Prettier configuration file. In my example I have two subfolders, and there is a configuration file in each subfolder:
I like using JSON configuration format so my code editor helps me. In fact, VSCode understands the Prettier configuration file format via the built-in json schema. So when I edit
projectA/.prettierrc.json file, I get intelligent tooltips.
Prettier tries to enforce the same code style without 100s of options, thus there are just a few settings you can change. Here are settings I am using in the first project to make it look "traditional" ES5
The second project uses more modern style without semi-colons and with trailing commas.
To use the Prettier we have just installed from VSCode we need to install the Prettier VSCode extension:
- Launch VS Code Quick Open (Ctrl+P)
- Run the following command
ext install esbenp.prettier-vscode
Because you might have global settings related to code formatting, I prefer having in each repository a file with local workspace VSCode settings. I commit this file
.vscode/settings.json to source control to make sure everyone uses the same extension to format the code.
projectA/index.js file by saving it.
Notice the double quotes, semi-colons, etc - Prettier has applied the settings from
projectA/.prettierrc.json. It also split long object across multiple lines to make it easier to read.
projectB/index.js gets formatted by Prettier using different local settings and ends up looking different.
Single quotes, no semi-colons, trailing commas.
Format files from CLI
Formatting every file as you save it is nice, but we can also format ALL source files at once using Prettier CLI. In the
package.json add a script to format files matching the mask and to write them back to disk.
Run this NPM script and the files will be formatted to follow the Prettier style
$ npm run format
Format staged files on commit
Whenever we work with files locally, we might accidentally commit them without proper styling. That's where Git hooks and formatting staged files comes in handy. To consistently format all files before committing and then commit changes, I recommend using husky + lint-staged combination of tools.
package.json set the following
$ g done "add husky and lint-staged"
Of course, you can skip the Git pre-commit hook by committing with
Catch mis-formatted files on CI
You can really enforce the formatting before pushing code to the central repository by running Prettier on CI and then detecting any changed files. Just run stop-build after running Prettier.
If any of the source files were reformatted by Prettier, the
stop-only will detect changed source files using Git information and will exit with an error. It will list the changed files, something like this:
⚠️ there are 2 changed files
Prettier has built-in command
--check that validates code files against formatting. Using it from a script in
Then on CI we can call the script right after
Let's say one of the files has not been formatted.
$ npm run check
Nothing happens on save
You are saving a file in VSCode ... and the code does not change. This could be due to three issues:
- Make sure local workspace settings have auto-format on save enabled. Open
.vscode/settings.jsonfile and confirm:
- VSCode Prettier extension is configured as the default formatter.
- Formatting on save is enabled
- Prettier extension might be disabled by VSCode. Make sure the word "Prettier" appears on the Status Bar and has check mark symbol next to it. To check:
- Right click on the Status Bar. Make sure the "Prettier" extension appears there is displayed.
- Make sure there is a checkmark next to the "Prettier" in the Status Bar. Sometimes after enabling the extension, it is loaded, but not enabled.
One thing I have noticed that sometimes saving a file enables Prettier if the
.vscode/settings.json have the extension enabled for this workspace. For example in this animation I am saving the file with double quotes around a string, and magically the Prettier extension gets the check mark and does its job. Don't ask.
If everything else fails, quit VSCode and start it again.
Code formatting is wrong
Here is a little animation that shows a file being saved with Prettier setting "trailingComma: true", yet the comma gets deleted somehow.
Check if there are OTHER code formatting extensions installed and disable them for this workspace. For some reason, VSCode can use globally installed extension overwriting local setting. Don't ask. In my case, I had "Prettier-Standard" extension enabled globally. After disabling the "Prettier-Standard" for the current workspace, Prettier extension started working as expected.
Why can't VSCode save the list of disabled extensions in
Sometimes you have files that should not be formatted: auto-generated source files, saved snapshots, etc. You can list file masks to ignore in file
snapshots folders use
Saving without formatting
If you ever work in someone else's project, please respect their formatting. In order to avoid reformatting the entire file when you save it from VSCode, save it without formatting. Run "Command + Shift + P" to open the Command Palette and type "save without" until you see "File: Save without Formatting" command - use that.
Temporarily disable formatting
There is also an extension that temporarily disables format on save feature called Formatting Toggle. Install it in your VSCode and whenever you want to temporarily disable Prettier on save, click on the "Formatting" toggle in the status bar.
Use Eslint with Prettier
Static linters, like ESLint can catch the assignment to a constant variable, so we need both:
- Prettier will reformat the code to be consistent in style
- ESLint will analyze the meaning of code and catch potential problems
Disable style rules in ESLint
ESLint runs a long list of rules against the code, and some of these rules are stylistic, and can conflict with Prettier's style. Thus we need to configure ESLint to skip those rules. This configuration is in module eslint-config-prettier. Install it
npm i -D eslint eslint-config-prettier
and can be added to your project
.eslintrc.json file. ESLint will not run without a valid configuration file.
Now when you run ESLint against this file
const name = 'Joe'; name = 'Mary'
Then ESLint will catch the
const assignment error; it will also catch that the variable
name is never used after assignment.
npx eslint projectC/index.js
Integrate ESLint in VSCode
Since we are using VSCode, it makes sense to install ESLint VSCode extension called
Open Command Pallette with Command + P
ext install dbaeumer.vscode-eslint
Enable this extension in VSCode workspace settings
You can see these errors for yourself by opening
projectC/index.js in VSCode from the example repo.
Run Prettier from ESLint
Since ESLint can detect and fix many of the errors it detects automatically, let's tell ESLint to run Prettier too. Here is the recommended setup
Install ESLint Prettier config and plugin
npm i -D eslint-config-prettier eslint-plugin-prettier
Point ESLint at the recommended settings which include Prettier styles
Notice in the screenshot below how ESLint warnings in VSCode editor include style errors from Prettier.
If we run ESLint with
--fix flag, it will use Prettier to auto format code, solving both stylistic and semantic problems.
If you decide to use ESLint with Prettier rules and have configured
husky to run
lint-staged, point it at
eslint --fix instead of
VSCode + ESLint + Prettier setup
Let's configure VSCode to use ESLint to auto-fix found issues, including Prettier. The workspace settings use
The animation shows how saving the file fixes both style and lint problems.
VSCode + ESLint + Prettier + TypeScript setup
First, if you have previous installed TSLint extension
vscode-tslint for VSCode, uninstall it - let ESLint do everything.
Second, install a new parser and plugin modules
npm i -D @typescript-eslint/parser @typescript-eslint/eslint-plugin
Then set the VSCode workspace settings to lint TypeScript files
And now you should see ESLint + Prettier errors and warnings in VSCode
Note: there is a bug in VSCode + ESLint extension where Prettier is not found. If you open Prettier console you can see the error, there is an open issue
So we see the lint and style errors, yet cannot reformat the code automatically on save. To work around this issue, use NPM script command.
Run this command and it should reformat the TS files and fix most ESLint issues.
Use Prettier + ESLint + Cypress
One final touch. If you write Cypress end-to-end tests, there is an official cypress-io/eslint-plugin-cypress plugin that can catch some common test mistakes. You can find an example "test" in
First, install the plugin
npm i -D eslint-plugin-cypress
Then extend ESLint settings
Let's say your test tries to get back an element using
// typical Cypress test
This WON'T work -
cy.get does not return an element, like a Promise, the found element will be passed down the command chain. Notice how ESLint shows an error if you try to assign the value of the