⬆️ Updates eslint-config-prettier to v9 #822
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
|
Hey! Changelogs info seems to be missing or might be in incorrect format. |
|
Pull request by bot. No need to analyze |
|
Thanks for opening an issue! Make sure you've followed CONTRIBUTING.md. |
Hello from PR HelperIs your PR ready for review and processing? Mark the PR ready by including If you still have work to do, even after marking this ready. Put the PR on hold by including |
|
Thanks for the PR! This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged. |
|
Updated dependencies detected. Learn more about Socket for GitHub ↗︎
|
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is bin script shell injection?This package re-exports a well known shell command via an npm bin script. This is possibly a supply chain attack Packages should not export bin scripts which conflict with well known shell commands Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
This PR contains the following updates:
^6.15.0->^9.0.0Release Notes
prettier/eslint-config-prettier (eslint-config-prettier)
v9.1.0Compare Source
ESLINT_CONFIG_PRETTIER_NO_DEPRECATEDenvironment variable.v9.0.0Compare Source
"unicode-bom": "off"to your config to disable it again, or run ESLint with--fixto fix all files according to the rule (add or remove BOM). Thanks to Nicolas Stepien (@nstepien)!v8.10.0Compare Source
v8.9.0Compare Source
v8.8.0Compare Source
v8.7.0Compare Source
v8.6.0Compare Source
v8.5.0Compare Source
v8.4.0Compare Source
v8.3.0Compare Source
v8.2.0Compare Source
v8.1.0Compare Source
v8.0.0Compare Source
Changed: All configs have been merged into one!
To upgrade, change:
{ "extends": [ "some-other-config-you-use", "prettier", "prettier/@​typescript-eslint", "prettier/babel", "prettier/flowtype", "prettier/react", "prettier/standard", "prettier/unicorn", "prettier/vue" ] }Into:
{ "extends": [ "some-other-config-you-use", "prettier" ] }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]:
{ "extends": [ "some-other-config-you-use", "plugin:prettier/recommended" ] }(The ["prettier/prettier" config][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).
v7.2.0Compare Source
v7.1.0Compare Source
v7.0.0Compare Source
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.{ "extends": ["prettier", "prettier/prettier"], "plugins": ["prettier"], "rules": { "prettier/prettier": "error" } }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-tabsis now a validatable rule. If you use it, you should enableallowIndentationTabsso that the rule works regardless of your Prettier config:{ "rules": { "no-tabs": ["error", { "allowIndentationTabs": true }] } }Changed: The CLI helper tool is now called just
eslint-config-prettierinstead ofeslint-config-prettier-check. This is so thatnpx eslint-config-prettieralways works regardless of whether you have already installedeslint-config-prettieror not: If you have, the local installation is used; if you haven’t,npxdownloads a temporary copy.Changed: The CLI helper tool no longer requires you to pipe the output of
eslint --print-configto 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.
Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Moscow, 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.