⬆️ Updates eslint-config-prettier to v8 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-config-prettier	^6.15.0 -> ^8.10.0

---

Release Notes

prettier/eslint-config-prettier (eslint-config-prettier)

v8.10.0

Compare Source

• Added: [max-statements-per-line]. Thanks to @​Zamiell!

v8.9.0

Compare Source

• Added: [vue/array-element-newline]. Thanks to @​xcatliu!

v8.8.0

Compare Source

• Added: [@​typescript-eslint/lines-around-comment]. Thanks to @​ttionya!

v8.7.0

Compare Source

• Added: [@​typescript-eslint/block-spacing]. Thanks to @​ttionya!
• Added: [@​typescript-eslint/key-spacing]. Thanks to @​ttionya!

v8.6.0

Compare Source

• Added: [vue/multiline-ternary]. Thanks to @​xcatliu!

v8.5.0

Compare Source

• Added: [@​typescript-eslint/space-before-blocks]. Thanks to Masafumi Koba (@​ybiquitous)!

v8.4.0

Compare Source

• Added: [vue/quote-props]. Thanks to @​xcatliu!

v8.3.0

Compare Source

• Added: Support for [@​babel/eslint-plugin]. Thanks to Chip Zhang (@​ChipZhang) for the heads-up! ([eslint-plugin-babel] is still supported, too.)

v8.2.0

Compare Source

• Added: [flowtype/quotes]. Thanks to Martin Zlámal (@​mrtnzlml)!

v8.1.0

Compare Source

• Added: [flowtype/object-type-curly-spacing].
• Added: Dummy files for the configs removed in 8.0.0. The dummy files throw an error that try to guide you how to upgrade.

v8.0.0

Compare 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.0

Compare Source

• Added: [@​typescript-eslint/object-curly-spacing].
• Added: [react/jsx-newline].

v7.1.0

Compare Source

• Added: [unicorn/empty-brace-spaces]. Thanks to fisker Cheung (@​fisker)!

v7.0.0

Compare 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-tabs is now a validatable rule. If you use it, you should enable allowIndentationTabs so 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-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.

  Before:

  npx eslint --print-config index.js | npx eslint-config-prettier-check
  

  After:

  npx eslint-config-prettier index.js
  

• 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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[changelogg]

Hey! Changelogs info seems to be missing or might be in incorrect format.
Please use the below template in PR description to ensure Changelogg can detect your changes:
- (tag) changelog_text
or
- tag: changelog_text
OR
You can add tag in PR header or while doing a commit too
(tag) PR header
or
tag: PR header
Valid tags: added / feat, changed, deprecated, fixed / fix, removed, security, build, ci, chore, docs, perf, refactor, revert, style, test
Thanks!
For more info, check out changelogg docs

[github-actions]

🏷️ [bumpr] Next version:v2.0.2 Changes:v2.0.1...AlexRogalskiy:renovate/eslint-config-prettier-8.x

[viezly]

Pull request by bot. No need to analyze

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Bin script shell injection	npm	6.14.11	Bin Script: which	@semantic-release/[email protected], @semantic-release/[email protected], @semantic-release/[email protected], @semantic-release/[email protected], @semantic-release/[email protected], @semantic-release/[email protected], [email protected] via package.json

Next steps

What 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 dependency

Take 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 package

If 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 risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore [email protected]

[socket-security]

Removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: [email protected]