Atom package to format your code using Prettier.
Problems with Latest Release (v0.55.0)?
We have recently switched to deferring most options to Prettier via a .prettierrc (or similar) file instead of specifying your options via the Atom package. This is to accommodate Prettier "plugins" which introduce all sorts of new functionality but can't work with the old paradigm.
However, this requires Prettier v1.13.4 or greater. If you are not ready to migrate, you can revert prettier-atom like this:
apm install email@example.com
apm install prettier-atom
Or go to Settings → Install and search for
Make sure to restart Atom after the package is installed.
How to use
There are two ways to format your code:
- Automatically format on save (requires enabling in Packages → Prettier → Toggle Format on Save)
- Run the command
Prettier: Formatto invoke Prettier manually
- Windows/Linux: ctrl + alt + f
- Mac: control + option + f
Prettier will search up the file tree looking for a prettier config to use. If none is found, Prettier will use its default settings.
Prettier will also respect your
What version of Prettier gets used?
By default, we use the prettier instance in your project's
node_modules directory. We highly recommend adding Prettier to your dependencies so that your team, CI tooling, and any scripts using Prettier all format code exactly the same way.
If Prettier can't be found in your project's node modules, then we fall back to using the version that comes bundled with the prettier-atom package (version changes are documented in the CHANGELOG).
Configuring default rules
Some users may not wish to create a new Prettier config for every project. Because Prettier searches recursively up the filepath, you can place a global prettier config at
~/.prettierrc to be used as a fallback.
There are three ways to use ESLint with Prettier and prettier-atom:
1. Use ESLint to run Prettier
You can opt not to use prettier-atom and instead configure ESLint to run prettier. (see details)
2. Turn off ESLint's Formatting Rules
You can disable ESLint rules for things that Prettier itself fixes. This allows both tools to run alongside each other without conflicting with one another. (see details)
3. Use prettier-eslint
The prettier-eslint package (shipped with prettier-atom) will recursively search up the file tree for your ESLint settings and infer the corresponding Prettier settings to use when formatting. After formatting, prettier-eslint will invoke ESLint to fix remaining issues. Check the "ESLint Integration" checkbox to enable.
Note: If you are using the linter-eslint package alongside prettier-atom, please ensure you have unchecked its "Fix on save" checkbox. Leaving it enabled will cause a race condition between prettier-atom and linter-eslint. After it has finished formatting your code, prettier-atom will automatically invoke the linter package's
lintcommand for you.
The prettier-stylelint package (shipped with prettier-atom) derives prettier settings from your stylelint configuration to use when formatting. After formatting, prettier-stylelint will invoke Stylelint to fix remaining issues. Check the "Stylelint Integration" checkbox to enable.
Note: prettier-atom automatically detects when you are in an Atom scope that stylelint supports and switches to using it instead of normal Prettier when formatting that file.
Troubleshooting formatting problems
If Prettier is not formatting something properly, please open an issue on the Prettier repository, not this repository.
This repository was created by James Long to go along with his Prettier project. Kent C. Dodds extended Prettier to add
eslint --fix integration as prettier-eslint and forked the original
prettier-atom plugin to create the
prettier-eslint-atom plugin. Because it became clear that the plugins were very similar and thus maintenance made easier by combining the two, Rob Wise merged
prettier-eslint-atom back into
Thanks goes to these people (emoji key):
This project follows the all-contributors specification. Contributions of any kind are welcome!