A Visual Studio Code Extension to format JavaScript and TypeScript code using the prettier-eslint package.

Please create an issue before adding a rating. Keep in mind that I work full-time and I am the only contributor currently. I'd LOVE to have more contributors. See the Contributing section below.

This extension requires the following NPM packages to be installed either locally or globally:

• prettier@1.9.1
• eslint@6.8.0
• @typescript-eslint/parser@^3.0.0 and typescript@^3.9.3 (Only for TypeScript projects)
• vue-eslint-parser@~7.1.0 (Only for Vue projects)

Support for Prettier 2 and ESLint 8

README

1. Open Extensions
2. Search Prettier ESLint
3. For a new installation, click down arrow next to Install button. Choose Install Pre-Release Version

4. For existing installation, click Prettier ESLint. In the right screen, click Switch to Pre-Release Version button

These projects are setup to work with the VS Code Prettier ESLint extension. Use them as a boilerplate for your project or as a reference for an existing project. If you don't see an example for your tech stack, create a PR of a working example.

• JavaScript
• JavaScript with Vue
• TypeScript
• TypeScript with Vue

1. Check for an error by opening the View menu and click Output
2. Select Prettier ESLint from the dropdown to the right

3. Open a JavaScript (.js or .jsx) or TypeScript (.ts or .tsx) file
4. Press CTRL + SHIFT + P (Windows/Linux) or CMD + SHIFT + P (macOS) to open the command palette
5. Start typing Format Document With and select Prettier ESLint
6. Click on Output to open the panel
7. If you see Error: Cannot find module, quit and restart Visual Studio Code
8. If restarting did not work:
   • Make sure you have the required packages installed locally (global installations don't work sometimes)
   • Repeat Step 8

Notes:

• The Prettier extension is not required.

• The ESLint extension is not required. However, it is needed to have lint errors show while editing your file.

1. In your project, install devDependencies

   npm install --save-dev eslint@6.8.0 prettier@1.9.1

   OR

   yarn add -D eslint@6.8.0 prettier@1.9.1

2. For TypeScript projects (.ts & .tsx files) install additional package under devDependencies

   npm install --save-dev @typescript-eslint/parser@^3.0.0

   OR

   yarn add -D @typescript-eslint/parser@^3.0.0

3. For Vue projects (.vue files) install additional package under devDependencies

   npm install --save-dev vue-eslint-parser@~7.1.0

   OR

   yarn add -D vue-eslint-parser@~7.1.0

1. Install the extension
2. Quit VS Code
3. Restart VS Code

1. Open the file you want to format
2. Press CTRL + SHIFT + P (Windows/Linux) or CMD + SHIFT + P (macOS) to open the command palette
3. Start typing Format Document With and select it
4. Choose the bottom item Configure Default Formatter
5. Choose Prettier ESLint

Once installed, open a JavaScript (.js or .jsx) or TypeScript (.ts or .tsx) file. Press SHIFT + OPTION + F (macOS) or SHIFT + ALT + F (Windows/Linux) to format a file.

You can enable the Format on Save setting to avoid entering the command all the time.

1. Set Prettier Eslint as the default formatter as detailed above
2. Open User or Workspace settings

• On Windows/Linux - File > Preferences > Settings
• On MacOS - Code > Preferences > Settings

3. Start typing Format on and select it
4. Check Format on Save (found mid-page in the right panel)
5. Ensure both Format on Input and Format on Paste are disabled. They are not supported functionality

Afterward, the file should format automatically once you save it

For the best performance, change Auto Save to onFocusChanged. This will have the editor save changes when you switch to another file or another program. The default setting makes the file save after you stop typing for an interval. This causes the formatter to run frequently thus taking more computer resources.

1. Open User or Workspace settings

• On Windows/Linux - File > Preferences > Settings
• On macOS - Code > Preferences > Settings

2. Start typing Auto Save and select onFocusChanged

The extension uses your ESLint and Prettier configuration files. These files are resolved starting from the location of the file being formatted, and searching up the file tree until a config file is (or isn't) found.

(From https://eslint.org/docs/user-guide/configuring)

Use a JavaScript, JSON or YAML file to specify configuration information for an entire directory and all of its subdirectories. This can be in the form of an .eslintrc.* file or an eslintConfig field in a package.json file.

(From https://prettier.io/docs/en/configuration.html)

Prettier uses cosmiconfig for configuration file support. This means you can configure prettier via (in order of precedence):

• A "prettier" key in your package.json file.
• A .prettierrc file, written in JSON or YAML, with optional extensions: .json/.yaml/.yml (without extension takes precedence).
• A .prettierrc.js or prettier.config.js file that exports an object.
• A .prettierrc.toml file, written in TOML (the .toml extension is required).

If you have suggestions for how this extension could be improved, or want to report a bug, open an issue! I'd love all and any contributions. If you are interested in contributing to the project, check out the Contributing Guide.

Thanks goes to these wonderful people (emoji key):

Rebecca Vest 💬 💻 📖 🚇 🐛 🤔 👀 ⚠️

Thomas Bekaert 💻

This project follows the all-contributors specification. Contributions of any kind welcome!