chore(deps-dev): bump eslint-plugin-prettier from 5.0.0 to 5.2.3

[dependabot]

Bumps eslint-plugin-prettier from 5.0.0 to 5.2.3.

Release notes

Sourced from eslint-plugin-prettier's releases.

v5.2.3

Patch Changes

• #703 9c6141f Thanks @​BPScott! - Add name field to recommended flat config

v5.2.2

Patch Changes

• #700 aa5b59f Thanks @​ntnyq! - fix: report node when loc not found

What's Changed

• docs(README): fixes legacy ESlint configs link by @​2KAbhishek in prettier/eslint-plugin-prettier#686
• fix: report node when loc not found by @​ntnyq in prettier/eslint-plugin-prettier#700

New Contributors

• @​2KAbhishek made their first contribution in prettier/eslint-plugin-prettier#686
• @​ntnyq made their first contribution in prettier/eslint-plugin-prettier#700

Full Changelog: prettier/eslint-plugin-prettier@v5.2.1...v5.2.2

v5.2.1

Patch Changes

• #668 ac036cc Thanks @​OrlovAlexei! - build(deps): Bump synckit from 0.8.6 to 0.9.1

v5.1.3

Patch Changes

• #629 985b33c Thanks @​JounQin! - chore: add package.json into exports map

Full Changelog: prettier/eslint-plugin-prettier@v5.1.2...v5.1.3

v5.1.2

5.1.2

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

  What means the following is unnecessary anymore when using with eslint-mdx/eslint-plugin-mdx!

  [
    {
      files: ["**/*.md"],
      rules: { "prettier/prettier": ["error", { parser: "markdown" }] },

... (truncated)

Changelog

Sourced from eslint-plugin-prettier's changelog.

5.2.3

Patch Changes

• #703 9c6141f Thanks @​BPScott! - Add name field to recommended flat config

5.2.2

Patch Changes

• #700 aa5b59f Thanks @​ntnyq! - fix: report node when loc not found

5.2.1

Patch Changes

• #668 ac036cc Thanks @​OrlovAlexei! - build(deps): Bump synckit from 0.8.6 to 0.9.1

5.2.0

Minor Changes

• #652 f170011 Thanks @​Logicer16! - feat: support parsing html via @html-eslint/parser natively

5.1.3

Patch Changes

• #629 985b33c Thanks @​JounQin! - chore: add package.json into exports map

5.1.2

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

  What means the following is unnecessary anymore when using with eslint-mdx/eslint-plugin-mdx!

  [
    {
      files: ["**/*.md"],
      rules: { "prettier/prettier": ["error", { parser: "markdown" }] },
    },
    {
      files: ["**/*.mdx"],

... (truncated)

Commits

• 6fd7ba1 chore: release eslint-plugin-prettier (#704)
• 190d6f9 build(deps): Bump synckit from 0.9.1 to 0.9.2 (#705)
• 9cf6a01 build(deps-dev): Bump svelte from 4.2.8 to 4.2.19 (#677)
• 9c6141f chore: add plugin name to flat recommended config (#703)
• 35a5cd0 chore: bupm eslint-plugin-comments (#702)
• df123a5 chore: release eslint-plugin-prettier (#701)
• e272d7c chore: use double quote for changesets/changelog files
• aa5b59f fix: report node when loc not found (#700)
• 37d87ea chore: update FUNDING.yml
• b307125 docs(README): fixes legacy ESlint configs link (#686)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6120c79

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR