Bump eslint-plugin-prettier from 5.0.0 to 5.1.2

[dependabot]

Bumps eslint-plugin-prettier from 5.0.0 to 5.1.2.

Release notes

Sourced from eslint-plugin-prettier's releases.

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" }] },
    },
    {
      files: ["**/*.mdx"],
      rules: { "prettier/prettier": ["error", { parser: "mdx" }] },
    },
  ]

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

v5.1.1

5.1.1

Patch Changes

• #619 b5c0dc5 Thanks @​JounQin! - chore: skip formatting inline scripts in pug files

v.5.1.0

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,
  ];

... (truncated)

Changelog

Sourced from eslint-plugin-prettier's changelog.

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'],
      rules: { 'prettier/prettier': ['error', { parser: 'mdx' }] },
    },
  ]

5.1.1

Patch Changes

• #619 b5c0dc5 Thanks @​JounQin! - chore: skip formatting inline scripts in pug files

5.1.0

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

... (truncated)

Commits

• d102278 chore: release eslint-plugin-prettier (#624)
• b02fe90 chore: bump all upgradable (dev)Dependencies (#625)
• 2b09e7f feat: support parsing markdown via eslint-mdx natively (#621)
• 5f762df docs: change open collective funding info (#626)
• 8210e44 fix: add package.json exports field (#623)
• 5a51733 chore: release eslint-plugin-prettier (#620)
• b5c0dc5 chore: skip formatting inline scripts in pug files (#619)
• 183f45c chore: release eslint-plugin-prettier (#604)
• 3856413 Add flat recommended config (#616)
• 78c8b80 Use flat config for the project's eslint configuration (#615)
• 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: 009bed1

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