You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For flat config users, the previous "eslint-config-prettier" entry still works, but "eslint-config-prettier/flat" adds a new name property for config-inspector, we just can't add it for the default entry for compatibility.
Added: The CLI helper tool now works with eslint.config.js (flat config). Just like ESLint itself, the CLI tool automatically first tries eslint.config.js and then eslintrc, and you can force which one to use by setting the ESLINT_USE_FLAT_CONFIG environment variable. Note that the config of eslint-config-prettier has always been compatible with eslint.config.js (flat config) – it was just the CLI tool that needed updating. On top of that, the docs have been updated to mention how to use both eslint.config.js (flat config) and eslintrc, and the tests now test both config systems.
Changed: unicode-bom is no longer turned off. Prettier preserves the BOM if you have one, and does not add one if missing. It was wrong of eslint-config-prettier to disable that rule. If you get ESLint errors after upgrading, either add "unicode-bom": "off" to your config to disable it again, or run ESLint with --fix to fix all files according to the rule (add or remove BOM). Thanks to Nicolas Stepien (@nstepien)!
The "prettier" config now includes not just ESLint core rules, but also rules from all plugins. Much simpler!
So … what’s the catch? Why haven’t we done this earlier? Turns out it’s just a sad mistake. I (@lydell) was confused when testing, and thought that turning off unknown rules in a config was an error. Thanks to Georgii Dolzhykov (@thorn0) for pointing this out!
(The "prettier/prettier" config still exists separately. It’s the odd one out. The main "prettier" config does not include the rules from it.)
Changed: The CLI helper tool now only prints warnings for arrow-body-style and prefer-arrow-callback, just like other “special rules.” This means that if you’ve decided to use those rules and eslint-plugin-prettier at the same time, you’ll get warnings but exit code zero (success).
Changed: arrow-body-style and prefer-arrow-callback are no longer turned off by default. They only need to be turned off if you use eslint-plugin-prettier. If you do, add "prettier/prettier" to your "extends" array to turn them off again.
Alternatively, update eslint-plugin-prettier to version 3.2.0 or later which automatically turns off these two rules in its "plugin:prettier/recommended" config.
The CLI helper tool only warns about these rules if you have the "prettier/prettier"rule enabled for a file.
Changed: no-tabs is now a validatable rule. If you use it, you should enable allowIndentationTabs so that the rule works regardless of your Prettier config:
Changed: The CLI helper tool is now called just eslint-config-prettier instead of eslint-config-prettier-check. This is so that npx eslint-config-prettier always works regardless of whether you have already installed eslint-config-prettier or not: If you have, the local installation is used; if you haven’t, npx downloads a temporary copy.
Changed: The CLI helper tool no longer requires you to pipe the output of eslint --print-config to it. Instead, it does that automatically for you via ESLint API:s added in ESLint v7.
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:
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.)
Changed: arrow-body-style and prefer-arrow-callback are now marked as special rules, since they might cause problems if using eslint-plugin-prettier and --fix. They are turned off by default, and the CLI helper tool will warn about them (but not error if you do enable them). This won’t break your linting checks, but do note that these rules will be disabled unless you explicitly enable them again, and that you might see new warnings when running the CLI helper tool.
Fixed: The eslint-plugin-vue change from 3.4.0 has been reverted. That change requires eslint-plugin-vue@5, while many use eslint-plugin-vue@4. In other words, it was an accidental breaking change. Also, after thinking about it some more, it makes sense to have a Prettier-specific list of rules, rather than using the vue/no-layout-rules list, since there can be layout rules that don’t conflict with but rather complement Prettier.
Added: New eslint-plugin-vue rules coming in the next version after 5.1.0.
Improved: The eslint-plugin-vue integration is now using the vue/no-layout-rules config behind the scenes, so it should automatically stay up-to-date when new eslint-plugin-vue versions are released. Thanks to Michał Sajnóg (@michalsnik)!
Changed: The quotes rule is now allowed to be used to forbid unnecessary backticks. This means that the CLI helper tool no longer can automatically validate it, so you’ll need to refer the quotes special rule documentation. Thanks to Nick Petruzzelli (@npetruzzelli)!
Changed/Improved: The CLI helper tool is now more helpful.
The options of special rules are now validated if possible. If a special rule is enabled with non-conflicting options, the CLI no longer warns about it.
If only special rules that cannot be automatically checked are found, the CLI no longer exists with a non-zero exit code. Instead, it only warns about the rules.
Changed: The no-confusing-arrow is now a special rule again, since it might conflict with recent Prettier versions.
Removed: The react/wrap-multilines rule (which has been deprecated for a while), since it was removed in eslint-plugin-react@7.
Version 1.7.0 (2017-04-19)
Changed: The no-confusing-arrow is no longer a special rule, but simply turned off, since recent Prettier versions make it redundant.
Improved: The CLI helper tool now has a more helpful message for special rules, and exits with a different status code if only special rules were found. The exit codes are now documented as well.
Version 1.6.0 (2017-04-05)
Added: The curly rule. Thanks to Martin Rädlinger (@formatlos)!
Fixed: "extends": "prettier/react" now actually works.
Version 1.0.2 (2017-01-30)
Improved: CLI helper tool instructions.
Version 1.0.1 (2017-01-29)
No difference from 1.0.0. Just an npm publish mistake.
Version 1.0.0 (2017-01-29)
Initial release.
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone America/Chicago, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
If you want to rebase/retry this PR, check this box
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
9.26.0
->9.32.0
4.17.16
->4.17.20
20.17.46
->20.19.9
18.3.21
->18.3.23
8.32.0
->8.38.0
8.32.0
->8.38.0
9.26.0
->9.32.0
10.1.5
->10.1.8
5.4.0
->5.5.3
3.5.3
->3.6.2
8.4.0
->8.5.0
Release Notes
eslint/eslint (@eslint/js)
v9.32.0
Compare Source
v9.31.0
Compare Source
v9.30.1
Compare Source
v9.30.0
Compare Source
v9.29.0
Compare Source
v9.28.0
Compare Source
v9.27.0
Compare Source
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.38.0
Compare Source
🩹 Fixes
isolatedDeclarations
if enabled inconstructor
option (#11351)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.37.0
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.36.0
Compare Source
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.35.1
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.35.0
Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.34.1
Compare Source
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.34.0
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.33.1
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.33.0
Compare Source
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.32.1
Compare Source
🩹 Fixes
TSMappedType
with no type annotation (#11180)❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.38.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.37.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.36.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.35.1
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.35.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.34.1
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.34.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.33.1
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.33.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.32.1
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
eslint/eslint (eslint)
v9.32.0
Compare Source
v9.31.0
Compare Source
v9.30.1
Compare Source
v9.30.0
Compare Source
v9.29.0
Compare Source
v9.28.0
Compare Source
v9.27.0
Compare Source
prettier/eslint-config-prettier (eslint-config-prettier)
v10.1.8
Compare Source
eslint-config-prettier
10.1.5
Patch Changes
60fef02
Thanks @JounQin! - chore: addfunding
field intopackage.json
10.1.4
Patch Changes
94b4799
Thanks @silvenon! - fix(cli): do not crash on no rules configured10.1.3
Patch Changes
4e95a1d
Thanks @pilikan! - fix: this package iscommonjs
, align its types correctly10.1.2
Patch Changes
a8768bf
Thanks @Fdawgs! - chore(package): add homepage for some 3rd-party registry - see #321 for more details10.1.1
Patch Changes
#309
eb56a5e
Thanks @JounQin! - fix: separate the/flat
entry for compatibilityFor flat config users, the previous
"eslint-config-prettier"
entry still works, but"eslint-config-prettier/flat"
adds a newname
property for config-inspector, we just can't add it for the default entry for compatibility.See also #308
10.1.0
Minor Changes
56e2e34
Thanks @JounQin! - feat: migrate to exports field10.0.3
Patch Changes
#294
8dbbd6d
Thanks @FloEdelmann! - feat: add name to config#280
cba5737
Thanks @zanminkian! - feat: add declaration file10.0.2
Patch Changes
e750edc
Thanks @Fdawgs! - chore(package): explicitly declare js module type10.0.0
Major Changes
5be64be
Thanks @abrahamguo! - add support for @stylistic formatting rulesVersions before 10.0.0
Version 9.1.0 (2023-12-02)
ESLINT_CONFIG_PRETTIER_NO_DEPRECATED
environment variable.Version 9.0.0 (2023-08-05)
"unicode-bom": "off"
to your config to disable it again, or run ESLint with--fix
to fix all files according to the rule (add or remove BOM). Thanks to Nicolas Stepien (@nstepien)!Version 8.10.0 (2023-08-03)
Version 8.9.0 (2023-07-27)
Version 8.8.0 (2023-03-20)
Version 8.7.0 (2023-03-06)
Version 8.6.0 (2023-01-02)
Version 8.5.0 (2022-03-02)
Version 8.4.0 (2022-02-19)
Version 8.3.0 (2021-04-24)
Version 8.2.0 (2021-04-13)
Version 8.1.0 (2021-02-24)
Version 8.0.0 (2021-02-21)
Changed: All configs have been merged into one!
To upgrade, change:
Into:
The
"prettier"
config now includes not just ESLint core rules, but also rules from all plugins. Much simpler!So … what’s the catch? Why haven’t we done this earlier? Turns out it’s just a sad mistake. I (@lydell) was confused when testing, and thought that turning off unknown rules in a config was an error. Thanks to Georgii Dolzhykov (@thorn0) for pointing this out!
If you use eslint-plugin-prettier, all you need is plugin:prettier/recommended:
(The "prettier/prettier" config still exists separately. It’s the odd one out. The main
"prettier"
config does not include the rules from it.)Changed: The CLI helper tool now only prints warnings for arrow-body-style and prefer-arrow-callback, just like other “special rules.” This means that if you’ve decided to use those rules and eslint-plugin-prettier at the same time, you’ll get warnings but exit code zero (success).
Version 7.2.0 (2021-01-18)
Version 7.1.0 (2020-12-19)
Version 7.0.0 (2020-12-05)
Changed: At least ESLint 7.0.0 is now required.
Changed: arrow-body-style and prefer-arrow-callback are no longer turned off by default. They only need to be turned off if you use eslint-plugin-prettier. If you do, add
"prettier/prettier"
to your"extends"
array to turn them off again.Alternatively, update eslint-plugin-prettier to version 3.2.0 or later which automatically turns off these two rules in its
"plugin:prettier/recommended"
config.The CLI helper tool only warns about these rules if you have the
"prettier/prettier"
rule enabled for a file.Changed:
no-tabs
is now a validatable rule. If you use it, you should enableallowIndentationTabs
so that the rule works regardless of your Prettier config:Changed: The CLI helper tool is now called just
eslint-config-prettier
instead ofeslint-config-prettier-check
. This is so thatnpx eslint-config-prettier
always works regardless of whether you have already installedeslint-config-prettier
or not: If you have, the local installation is used; if you haven’t,npx
downloads a temporary copy.Changed: The CLI helper tool no longer requires you to pipe the output of
eslint --print-config
to it. Instead, it does that automatically for you via ESLint API:s added in ESLint v7.Before:
After:
Improved: The npm package is now 75% smaller.
Version 6.15.0 (2020-10-27)
Version 6.14.0 (2020-10-21)
Version 6.13.0 (2020-10-16)
Version 6.12.0 (2020-09-25)
Version 6.11.0 (2020-04-21)
Version 6.10.1 (2020-03-22)
npx
when running the CLI helper tool.Version 6.10.0 (2020-01-28)
Version 6.9.0 (2019-12-27)
Version 6.8.0 (2019-12-25)
Version 6.7.0 (2019-11-19)
Version 6.6.0 (2019-11-17)
Version 6.5.0 (2019-10-26)
Version 6.4.0 (2019-10-05)
Version 6.3.0 (2019-09-10)
Version 6.2.0 (2019-09-03)
Version 6.1.0 (2019-08-19)
Version 6.0.0 (2019-06-25)
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 totrue
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:
Into this:
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 ofeslint --print-config .
, useeslint --print-config path/to/main.js
.)Version 5.1.0 (2019-06-25)
Version 5.0.0 (2019-06-15)
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. 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:eslint --fix
if you prefer to enforce self-closing elements where possible. This should fix all the errors."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.Changed: Node.js 6 is no longer officially supported, but v5.0.0 should still work with it.
Version 4.3.0 (2019-05-16)
Version 4.2.0 (2019-04-25)
Version 4.1.0 (2019-02-26)
Version 4.0.0 (2019-01-26)
--fix
. They are turned off by default, and the CLI helper tool will warn about them (but not error if you do enable them). This won’t break your linting checks, but do note that these rules will be disabled unless you explicitly enable them again, and that you might see new warnings when running the CLI helper tool.Version 3.6.0 (2019-01-19)
Version 3.5.0 (2019-01-16)
vue/no-layout-rules
list, since there can be layout rules that don’t conflict with but rather complement Prettier.Version 3.4.0 (2019-01-13)
vue/no-layout-rules
config behind the scenes, so it should automatically stay up-to-date when new eslint-plugin-vue versions are released. Thanks to Michał Sajnóg (@michalsnik)!Version 3.3.0 (2018-11-11)
Version 3.2.0 (2018-11-10)
Version 3.1.0 (2018-09-22)
Version 3.0.1 (2018-08-13)
eslint --print-config
usage instructions.Version 3.0.0 (2018-08-13)
Version 2.10.0 (2018-08-13)
Version 2.9.0 (2017-11-26)
Version 2.8.0 (2017-11-19)
Version 2.7.0 (2017-11-01)
Version 2.6.0 (2017-09-23)
Version 2.5.0 (2017-09-16)
Version 2.4.0 (2017-09-02)
Version 2.3.0 (2017-06-30)
Version 2.2.0 (2017-06-17)
Version 2.1.1 (2017-05-20)
Version 2.1.0 (2017-05-13)
Version 2.0.0 (2017-05-07)
Changed/Improved: The CLI helper tool is now more helpful.
Changed: The no-confusing-arrow is now a special rule again, since it might conflict with recent Prettier versions.
Removed: The
react/wrap-multilines
rule (which has been deprecated for a while), since it was removed in eslint-plugin-react@7.Version 1.7.0 (2017-04-19)
Version 1.6.0 (2017-04-05)
Version 1.5.0 (2017-03-04)
Version 1.4.1 (2017-02-28)
Version 1.4.0 (2017-02-26)
Version 1.3.0 (2017-02-21)
Version 1.2.0 (2017-02-14)
Version 1.1.1 (2017-02-12)
Version 1.1.0 (2017-02-10)
Version 1.0.3 (2017-02-03)
"extends": "prettier/react"
now actually works.Version 1.0.2 (2017-01-30)
Version 1.0.1 (2017-01-29)
npm publish
mistake.Version 1.0.0 (2017-01-29)
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone America/Chicago, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.