Prettier Formatter for Visual Studio Code
Prettier is an opinionated code formatter. It enforces a consistent style by parsing your code and re-printing it with its own rules that take the maximum line length into account, wrapping code when necessary.
Your favorite language?
Install through VS Code extensions. Search for
Prettier - Code formatter
Visual Studio Code Market Place: Prettier - Code formatter
Can also be installed in VS Code: Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
ext install esbenp.prettier-vscode
To ensure that this extension is used over other extensions you may have installed, be sure to set it as the default formatter in your VS Code settings. This setting can be set for all languages or by a specific language.
This extension will use prettier from your project's local dependencies (recommended). When the
prettier.resolveGlobalModules is set to
true the extension can also attempt to resolve global modules. Should prettier not be installed locally with your project's dependencies or globally on the machine, the version of prettier that is bundled with the extension will be used.
To install prettier in your project and pin its version as recommended, run:
npm install prettier -D --save-exact
This extension supports Prettier plugins when you are using a locally or globally resolved version of prettier. If you have Prettier and a plugin registered in your
package.json, this extension will attempt to register the language and provide automatic code formatting for the built-in and plugin languages.
There are multiple options for configuring Prettier with this extension. You can use VS Code settings, prettier configuration files, or an
.editorconfig file. The VS Code settings are meant to be used as a fallback and are generally intended only for use on non-project files. It is recommended that you always include a prettier configuration file in your project specifying all settings for your project. This will ensure that no matter how you run prettier - from this extension, from the CLI, or from another IDE with Prettier, the same settings will get applied.
Using Prettier Configuration files to set formatting options is the recommended approach. Options are searched recursively down from the file being formatted so if you want to apply prettier settings to your entire project simply set a configuration in the root. Settings can also be configured through VS Code - however, these settings will only apply while running the extension, not when running prettier through the command line.
Configuring Default Options
Some users may not wish to create a new Prettier config for every project or use the VS Code settings. Because Prettier searches recursively up the file path, you can place a global prettier config at
~/.prettierrc to be used as a fallback.
You can also use the setting
prettier.configPath to provide a global configuration. However, be careful, if this is set this value will always be used and local configuration files will be ignored.
Visual Studio Code Settings
You can use VS Code settings to configure prettier. Settings will be read from (listed by priority):
- Prettier configuration file
- Visual Studio Code Settings (Ignored if any other configuration is present)
NOTE: If any local configuration file is present (i.e.
.prettierrc) the VS Code settings will NOT be used.
Using Command Palette (CMD/CTRL + Shift + P)
1. CMD + Shift + P -> Format Document
1. Select the text you want to Prettify
2. CMD + Shift + P -> Format Selection
Visual Studio Code provides default keyboard shortcuts for code formatting. You can learn about these for each platform in the VS Code documentation.
If you don't like the defaults, you can rebind
editor.action.formatSelection in the keyboard shortcuts menu of vscode.
Format On Save
You can turn on format-on-save on a per-language basis by scoping the setting:
// Set the default
// Enable per-language
Format selection works on several languages depending on what Prettier itself supports. The following languages currently are supported:
The preferred way of integrating with linters is to let Prettier do the formatting and configure the linter to not deal with formatting rules. You can see how this is done here. To continue to use Prettier and your linter we recommend you use the ESLint, TSLint or Stylelint extensions directly.
You can enable Auto-Fix on Save for ESLint, TSLint or Stylelint and still have formatting and quick fixes:
// For ESLint
// For TSLint
// For Stylelint
NOTE: If you are seeing conflicts between Prettier and ESLint this is because you don't have the right ESLint or TSLint rules set as explained in the Prettier documentation.
Legacy Prettier Linter Integration (unreliable, not recommended)
WARNING: There are numerous issues with this type of integration due to problems in the libraries like
prettier-eslint. See: #870, #137, #494, #1191, and others. Due to these problems, this feature will likely to be removed completely in future versions of this extension.
The legacy option for integrating linters with Prettier is to use
prettier-stylelint. In order to use these integrations you MUST install these modules in your project's
package.json along with dependencies like
This extension will automatically detect when you have these extensions installed and use them instead of
prettier by itself. For configuration of these linter integrations, see their respective documentation.
All prettier options can be configured directly in this extension. These settings are used as a fallback when no configuration file is present in your project, see the configuration section of this document for more details. For reference on the options see the prettier documentation.
These settings are specific to VS Code and need to be set in the VS Code settings file. See the documentation for how to do that.
Require a prettier configuration file to format files. Untitled files will still be formatted using the VS Code Prettier configuration even with this option set to
Supply the path to an ignore file such as
Files which match will not be formatted. Set to
null to not read ignore files.
Note, if this is set, this value will always be used and local ignore files will be ignored.
Supply a custom path to the prettier configuration file.
Note, if this is set, this value will always be used and local configuration files will be ignored. A better option for global defaults is to put a
~/.prettierrc file in your home directory.
Supply a custom path to the prettier module.
Controls the package manager to be used to resolve modules. This has only an influence if the
prettier.resolveGlobalModules setting is
true and modules are resolved globally. Valid values are
When enabled, this extension will attempt to use global npm or yarn modules if local modules cannot be resolved.
NOTE: This setting can have a negative performance impact, particularly on Windows when you have attached network drives. Only enable this if you must use global modules. It is recommended that you always use local modules when possible.
A list of languages IDs to disable this extension on.
Note: Disabling a language enabled in a parent folder will prevent formatting instead of letting any other formatter to run
Whether or not to take .editorconfig into account when parsing configuration. See the prettier.resolveConfig docs for details.
Failed to load module. If you have prettier or plugins referenced in package.json, ensure you have run
package.json is present in your project and it contains prettier, plugins, or linter libraries this extension will attempt to load these modules from your
node_module folder. If you see this error, it most likely means you need to run
npm install or
yarn install to install the packages in your
Your project is configured to use an outdated version of prettier that cannot be used by this extension. Upgrade to the latest version of prettier.
You must upgrade to a newer version of prettier.
This extension uses Application Insights to track anonymous feature usage and version info. We don't record IP addresses or any other personally identifiable information. The reason we track this data is simply to help with prioritization of features.
This extension respects the VS Code telemetry setting so if you have telemetry disabled in VS Code we will also not collect telemetry. See the Visual Studio Code docs for information on how to disable telemetry.