Update dependency eslint-config-prettier to v6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
eslint-config-prettier	devDependencies	major	^4.1.0 -> ^6.0.0

---

Release Notes

prettier/eslint-config-prettier

v6.9.0

Compare Source

• Added: [vue/max-len]. Thanks to @​xcatliu!

v6.8.0

Compare Source

• Added: [@​typescript-eslint/no-extra-semi]. Thanks to @​xcatliu!

v6.7.0

Compare Source

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

v6.6.0

Compare Source

• Added: New [eslint-plugin-vue] rules: [vue/dot-location] and
  [vue/keyword-spacing]. Thanks to @​xcatliu!

v6.5.0

Compare Source

• Added: Support for [excluding deprecated rules]. Thanks to Alex Ilyaev
  (@​alexilyaev)!

v6.4.0

Compare Source

• Added: [unicorn/no-nested-ternary]. Thanks to Yang Mingshan
  (@​yangmingshan)!

v6.3.0

Compare Source

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

v6.2.0

Compare Source

• Added: [@​typescript-eslint/quotes] (as a [special
  rule][@​typescript-eslint/quotes-special]). Thanks to Masafumi Koba
  (@​ybiquitous)!

v6.1.0

Compare Source

• Added: [function-call-argument-newline] (new in ESLint 6.2.0). Thanks to
  Masafumi Koba (@​ybiquitous)!

v6.0.0

Compare Source

• 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 to true 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:

  {
    "rules": {
      "no-confusing-arrow": ["error"]
    }
  }

  Into this:

  {
    "rules": {
      "no-confusing-arrow": ["error", { "allowParens": false }]
    }
  }

  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 of eslint --print-config ., use eslint --print-config path/to/main.js.)

v5.1.0

Compare Source

• Added: [react/jsx-curly-newline]. Thanks to Masafumi Koba (@​ybiquitous)!

v5.0.0

Compare Source

• 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][prettier-self-closing]. 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:

  • Run eslint --fix if you prefer to enforce self-closing elements where
    possible. This should fix all the errors.
  • Add "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][prettier-self-closing].

• Changed: Node.js 6 is no longer officially supported, but v5.0.0 should
  still work with it.

---

Renovate 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 if you modify the PR title to begin with "rebase!".

🔕 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

---

Newsflash: Renovate has joined WhiteSource, and is now free for all use. Learn more or view updated terms and privacy policies.

[dshenderson]

This PR is now covered by #238, so closing.

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 6.x releases. However, if you upgrade to 6.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.