chore(deps): update dependency eslint-config-prettier to v8 - abandoned

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-config-prettier	^6.11.0 -> ^8.0.0

---

Release Notes

prettier/eslint-config-prettier

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.

v6.15.0

Compare Source

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

v6.14.0

Compare Source

• Added: New [eslint-plugin-vue] rules: [vue/array-bracket-newline] and [vue/block-tag-newline]. Thanks to @​xcatliu!

v6.13.0

Compare Source

• Added: New rules in [eslint-plugin-vue] 7.0 (which supports Vue 3.0). Thanks to @​xcatliu!

v6.12.0

Compare Source

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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.