Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency eslint-plugin-prettier to v5 #3152

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 24, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-prettier 4.2.1 -> 5.2.1 age adoption passing confidence

Release Notes

prettier/eslint-plugin-prettier (eslint-plugin-prettier)

v5.2.1

Compare Source

Patch Changes

v5.1.3

Compare Source

Patch Changes

v5.1.2

Compare Source

Patch Changes
  • #​623 8210e44 Thanks @​BPScott! - Add exports mapping to package.json, to allow import eslintPluginRecommended from 'eslint-plugin-prettier/recommended' to work as expected.

    Strictly speaking this is a breaking change as it removes the ability for people to import from "eslint-plugin-prettier/eslint-plugin-prettier.js" and "eslint-plugin-prettier/recommended.js" but the former was never recommended in the first place and the latter has only been available for a few days.

  • #​621 2b09e7f Thanks @​JounQin! - feat: support parsing markdown via eslint-mdx natively

v5.1.1

Compare Source

Patch Changes

v5.1.0

Compare Source

Minor Changes
  • #​616 3856413 Thanks @​BPScott! - Add recommended config for the flat config format.

    If you are using flat config, import the recommended config from eslint-plugin-prettier/recommended. Like the legacy format recommended config, this automatically includes the contents of eslint-config-prettier.

    // eslint.config.js
    const eslintPluginPrettierRecommended = require('eslint-plugin-prettier/recommended');
    
    module.exports = [
      // Any other config imports go at the top
      eslintPluginPrettierRecommended,
    ];
Patch Changes
  • #​614 5270877 Thanks @​BPScott! - Add meta block to plugin. This improves debugging and cachebusting when using the new flat config

  • #​603 a63a570 Thanks @​filiptammergard! - fix: specify eslint-config-prettier as peer dependency

    It's already added to peerDependenciesMeta as optional, which means it should also be specified in peerDependencies.

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes
Minor Changes
Patch Changes

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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Aug 24, 2023

⚠ 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 click 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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/prettier
npm error   dev prettier@"2.8.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer prettier@">=3.0.0" from [email protected]
npm error node_modules/eslint-plugin-prettier
npm error   dev eslint-plugin-prettier@"5.1.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-06T19_34_31_870Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-06T19_34_31_870Z-debug-0.log

@renovate renovate bot force-pushed the renovate/eslint-plugin-prettier-5.x branch 15 times, most recently from 1177f4c to 74e2cd1 Compare August 31, 2023 00:43
@renovate renovate bot force-pushed the renovate/eslint-plugin-prettier-5.x branch 6 times, most recently from ca0a04e to c1a4654 Compare September 7, 2023 17:42
@renovate renovate bot force-pushed the renovate/eslint-plugin-prettier-5.x branch 5 times, most recently from 83b139e to d0665d1 Compare September 15, 2023 18:44
@renovate renovate bot force-pushed the renovate/eslint-plugin-prettier-5.x branch 3 times, most recently from 7c14cc1 to 89c9f7b Compare September 19, 2023 18:22
@renovate renovate bot force-pushed the renovate/eslint-plugin-prettier-5.x branch 10 times, most recently from 6bdde99 to 49bbfe8 Compare September 16, 2024 15:02
@renovate renovate bot force-pushed the renovate/eslint-plugin-prettier-5.x branch 7 times, most recently from 8959b63 to ce5241e Compare September 23, 2024 20:57
@renovate renovate bot force-pushed the renovate/eslint-plugin-prettier-5.x branch 3 times, most recently from a820701 to 5492599 Compare October 1, 2024 13:35
@renovate renovate bot force-pushed the renovate/eslint-plugin-prettier-5.x branch 8 times, most recently from 1428205 to ae41917 Compare October 21, 2024 17:04
@renovate renovate bot force-pushed the renovate/eslint-plugin-prettier-5.x branch from ae41917 to ff0988d Compare October 29, 2024 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants