-
Notifications
You must be signed in to change notification settings - Fork 5
fix(deps): update prettier (major) #173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-prettier
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
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
4b08367
to
8bffb3c
Compare
8bffb3c
to
0ce1f28
Compare
0ce1f28
to
0c1babc
Compare
0c1babc
to
1312b43
Compare
1312b43
to
ac14756
Compare
ac14756
to
41f200b
Compare
41f200b
to
a0d708f
Compare
a0d708f
to
e382f2e
Compare
e382f2e
to
2a2a672
Compare
2a2a672
to
c8859eb
Compare
c8859eb
to
b66d735
Compare
b66d735
to
467ef99
Compare
467ef99
to
b36aeb6
Compare
b36aeb6
to
640e624
Compare
640e624
to
4322c25
Compare
4322c25
to
1d2ade6
Compare
1d2ade6
to
23cc0db
Compare
6bd4f00
to
e4ebba4
Compare
e4ebba4
to
f4bf038
Compare
f4bf038
to
60f3bc2
Compare
60f3bc2
to
299f4ab
Compare
a589e17
to
2d1044e
Compare
2d1044e
to
468e5f9
Compare
6f12bf8
to
9f16e9b
Compare
9f16e9b
to
31e14a2
Compare
31e14a2
to
134a5fc
Compare
de3b4d3
to
f42d6ff
Compare
f42d6ff
to
7447a32
Compare
7447a32
to
0b05f90
Compare
f2d4a4d
to
86a75f2
Compare
fa9d727
to
5ac75e3
Compare
ee4442d
to
57da4e0
Compare
57da4e0
to
407b804
Compare
d097a2f
to
28bd0c5
Compare
1f80033
to
8499af8
Compare
8499af8
to
ba2d96e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Note
Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to
mend[bot]
.This notice will be removed on 2025-10-07.
This PR contains the following updates:
^9.0.0
->^10.1.8
^2.4.1
->^3.6.2
Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.
Release Notes
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)
v10.1.5
Compare Source
Patch Changes
60fef02
Thanks @JounQin! - chore: addfunding
field intopackage.json
v10.1.4
Compare Source
Patch Changes
94b4799
Thanks @silvenon! - fix(cli): do not crash on no rules configuredv10.1.3
Compare Source
Patch Changes
4e95a1d
Thanks @pilikan! - fix: this package iscommonjs
, align its types correctlyv10.1.2
Compare Source
Patch Changes
a8768bf
Thanks @Fdawgs! - chore(package): add homepage for some 3rd-party registry - see #321 for more detailsv10.1.1
Compare Source
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
v10.1.0
Compare Source
Minor Changes
56e2e34
Thanks @JounQin! - feat: migrate to exports fieldv10.0.3
Compare Source
Patch Changes
#294
8dbbd6d
Thanks @FloEdelmann! - feat: add name to config#280
cba5737
Thanks @zanminkian! - feat: add declaration filev10.0.2
Compare Source
Patch Changes
e750edc
Thanks @Fdawgs! - chore(package): explicitly declare js module typev10.0.1
Compare Source
eslint-config-prettier
10.0.1
What's Changed
@stylistic/eslint-plugin
by @abrahamguo in https://github.com/prettier/eslint-config-prettier/pull/272New Contributors
Full Changelog: prettier/eslint-config-prettier@v9.1.0...v10.0.1
v10.0.0
Compare Source
Major Changes
5be64be
Thanks @abrahamguo! - add support for @stylistic formatting rulesv9.1.2
Compare Source
v9.1.0
Compare Source
ESLINT_CONFIG_PRETTIER_NO_DEPRECATED
environment variable.prettier/prettier (prettier)
v3.6.2
Compare Source
diff
Markdown: Add missing blank line around code block (#17675 by @fisker)
v3.6.1
Compare Source
diff
TypeScript: Allow const without initializer (#17650, #17654 by @fisker)
Miscellaneous: Avoid closing files multiple times (#17665 by @43081j)
When reading a file to infer the interpreter from a shebang, we use the
n-readlines
library to read the first line in order to get the shebang.This library closes files when it reaches EOF, and we later try close the same
files again. We now close files only if
n-readlines
did not already closethem.
v3.6.0
Compare Source
diff
🔗 Release Notes
v3.5.3
Compare Source
v3.5.2
Compare Source
diff
Remove
module-sync
condition (#17156 by @fisker)In Prettier 3.5.0, we added
module-sync
condition topackage.json
, so thatrequire("prettier")
can use ESM version, but turns out it doesn't work if CommonJS and ESM plugins both imports builtin plugins. To solve this problem, we decide simply remove themodule-sync
condition, sorequire("prettier")
will still use the CommonJS version, we'll revisit untilrequire(ESM)
feature is more stable.v3.5.1
Compare Source
diff
Fix CLI crash when cache for old version exists (#17100 by @sosukesuzuki)
Prettier 3.5 uses a different cache format than previous versions, Prettier 3.5.0 crashes when reading existing cache file, Prettier 3.5.1 fixed the problem.
Support dockercompose and github-actions-workflow in VSCode (#17101 by @remcohaszing)
Prettier now supports the
dockercompose
andgithub-actions-workflow
languages in Visual Studio Code.v3.5.0
Compare Source
diff
🔗 Release Notes
v3.4.2
Compare Source
diff
Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796 by @tats-u)
Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.
U+30A0 can be used as the replacement of the
-
in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン=サーンス”).Fix comments print on class methods with decorators (#16891 by @fisker)
Fix non-idempotent formatting (#16899 by @seiyab)
This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.
v3.4.1
Compare Source
diff
Remove unnecessary parentheses around assignment in
v-on
(#16887 by @fisker)v3.4.0
Compare Source
diff
🔗 Release Notes
v3.3.3
Compare Source
diff
Add parentheses for nullish coalescing in ternary (#16391 by @cdignam-segment)
This change adds clarity to operator precedence.
Add parentheses for decorator expressions (#16458 by @y-schneider)
Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.
Support
@let
declaration syntax (#16474 by @sosukesuzuki)Adds support for Angular v18
@let
declaration syntax.Please see the following code example. The
If you want to rebase/retry this PR, check this box@let
declaration allows you to define local variables within the template:This PR was generated by Mend Renovate. View the repository job log.