Bump eslint-plugin-prettier from 4.2.1 to 5.1.2

[dependabot[bot]]

Bumps eslint-plugin-prettier from 4.2.1 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: https://github.com/prettier/eslint-plugin-prettier/compare/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 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)

[pull-request-quantifier-deprecated[bot]]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

``` Label : Extra Small Size : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .json : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.