Update dependency eslint-config-prettier to v8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-config-prettier	7.0.0 -> 8.3.0

---

Release Notes

prettier/eslint-config-prettier

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)!

---

Configuration

📅 Schedule: 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 WhiteSource Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you check the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: eslint-config-prettier@7.0.0
npm ERR! node_modules/eslint-config-prettier
npm ERR!   dev eslint-config-prettier@"8.3.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev eslint-config-prettier@"8.3.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: eslint@7.29.0
npm ERR! node_modules/eslint
npm ERR!   peer eslint@">=7.0.0" from eslint-config-prettier@8.3.0
npm ERR!   node_modules/eslint-config-prettier
npm ERR!     dev eslint-config-prettier@"8.3.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2021-06-22T17_53_12_274Z-debug.log