Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jun 29, 2019

This PR contains the following updates:

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

Release Notes

prettier/eslint-config-prettier

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: "every weekend" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR is stale, 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

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

@renovate renovate bot force-pushed the renovate/eslint-config-prettier-6.x branch from 6dbe3dd to 8d8dfce Compare July 1, 2019 19:57
@coveralls
Copy link

coveralls commented Jul 1, 2019

Coverage Status

Coverage remained the same at 95.428% when pulling 22ff336 on renovate/eslint-config-prettier-6.x into 4535d36 on master.

@renovate renovate bot force-pushed the renovate/eslint-config-prettier-6.x branch from 8d8dfce to 8d627e5 Compare July 1, 2019 20:09
@renovate renovate bot force-pushed the renovate/eslint-config-prettier-6.x branch 2 times, most recently from d7b9a1c to 28e1f8e Compare July 3, 2019 20:13
@renovate renovate bot force-pushed the renovate/eslint-config-prettier-6.x branch from 28e1f8e to 22ff336 Compare July 3, 2019 20:29
@austingreendev austingreendev merged commit c083a1f into master Jul 3, 2019
@austingreendev austingreendev deleted the renovate/eslint-config-prettier-6.x branch July 3, 2019 20:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants