eslint-config-prettier - npm Package Versions

Changed: The CLI helper tool now considers [no-confusing-arrow] to conflict if you use the default value of its allowParens option. The default was changed to true in ESLint 6, which conflicts with Prettier.

If the CLI helper tool gives you errors about this after upgrading, the solution is to change this:

{
  "rules": {
    "no-confusing-arrow": ["error"]
  }
}

Into this:

{
  "rules": {
    "no-confusing-arrow": ["error", { "allowParens": false }]
  }
}

The latter works in both ESLint 6 as well as in ESLint 5 and older.

Improved: eslint --print-config usage instructions. The CLI tool help text as well as the documentation has been updated to suggest commands that work in ESLint 6.0 as well as in ESLint 5 and older. (Instead of eslint --print-config ., use eslint --print-config path/to/main.js.)

Removed: [react/self-closing-comp]. This rule was added in v4.1.0 not because it conflicted with Prettier but because it was unnecessary when using Prettier. However, in v1.18.0 [Prettier stopped converting empty elements to self-closing elements][prettier-self-closing]. So the rule is not unnecessary anymore.

If you use Prettier v1.17.1 or older you should be able to upgrade eslint-config-prettier to v5.0.0 without having to do anything else.

If you use Prettier v1.18.0 or newer, you might get lint errors about for example changing <div></div> into <div />. You have two options:

• Run eslint --fix if you prefer to enforce self-closing elements where possible. This should fix all the errors.
• Add "react/self-closing-comp": "off" to your ESLint config if you use autofix from your editor and you face the same [issue as Prettier did][prettier-self-closing].

Changed: Node.js 6 is no longer officially supported, but v5.0.0 should still work with it.