chore(deps): update dependency eslint-plugin-prettier to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-plugin-prettier	3.3.1 -> 5.4.0

---

Release Notes

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

v5.4.0

Compare Source

Minor Changes

• #​736 59a0cae Thanks @​yashtech00! - refactor: migrate worker.js to worker.mjs

v5.3.1

Compare Source

Patch Changes

• #​734 dcf2c80 Thanks @​JounQin! - ci: enable NPM_CONFIG_PROVENANCE env

v5.3.0

Compare Source

Minor Changes

• #​674 6fe0c90 Thanks @​irsooti! - feat(types): prefer Config over FlatConfig when they're equal

v5.2.6

Compare Source

Patch Changes

• #​723 1451176 Thanks @​renovate! - fix(deps): bump synckit to v0.11.0

v5.2.5

Compare Source

Patch Changes

• #​721 4f5513d Thanks @​JounQin! - fix: clarify correct eslint-config-prettier peer range

v5.2.4

Compare Source

Patch Changes

• #​715 b8cfe56 Thanks @​JounQin! - chore: hourcekeeping, bump all (dev) deps

v5.2.3

Compare Source

Patch Changes

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

v5.2.2

Compare Source

Patch Changes

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

v5.2.1

Compare Source

Patch Changes

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

v5.1.3

Compare Source

Patch Changes

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

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

  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" }] },
    },
  ]

v5.1.1

Compare Source

Patch Changes

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

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

• #​588 21a7146 Thanks @​krist7599555! - fix: parserPath type might be undefined on Eslint Falt Config

v5.0.0

Compare Source

Major Changes

• #​508 910aeb6 Thanks @​JounQin! - feat!: bump peer eslint to ">=8.0.0" and node to "^14.18.0 || >=16.0.0"

• #​508 910aeb6 Thanks @​JounQin! - feat!: upgrade to prettier v3

Minor Changes

• #​508 910aeb6 Thanks @​JounQin! - feat: add typings support

Patch Changes

• #​548 82a3db8 Thanks @​fisker! - fix: add missing dependency synckit

• #​564 ae7a73c Thanks @​auvred! - fix: compatibility with prettier@3 without plugins

v4.2.1

Compare Source

Patch Changes

• #​485 5736ed5 Thanks @​JounQin! - chore: reuse prettierRcOptions instead of resolveConfig again

v4.2.0

Compare Source

Minor Changes

• #​483 7bd70b6 Thanks @​JounQin! - feat: support svelte out of box

  close #​472, close #​482

  We recommend to use eslint-plugin-svelte instead of eslint-plugin-svelte3.

v4.1.0

Compare Source

• feat: skip processing code blocks on specific languages like stylelint-prettier (#​415) (52eec48)
• build(deps): Bump minimist from 1.2.5 to 1.2.6 (#​464) (42bfe88)
• build(deps-dev): Bump graphql from 15.5.1 to 15.7.2 (#​442) (0158640)
• build(deps-dev): Bump @​graphql-eslint/eslint-plugin from 2.3.0 to 2.4.0 (#​444) (4bcaca2)
• chore(CI): add tests for ESLint 8 (#​428) (f3713be)
• README.md: HTTP => HTTPS (#​443) (44e1478)

v4.0.0

Compare Source

This breaking change drops support for old versions of ESLint, Prettier and
Node. You must use at least ESLint v7.28.0, Prettier v2.0.0 and Node v12.0.0.
Aside from that, usage of this plugin remains identical.

• v4 - Drop support for eslint 5/6, prettier 1, node 6/8 (#​429) (acb56f3)

v3.4.1

Compare Source

• build(deps): Bump glob-parent from 5.0.0 to 5.1.2 (#​420) (b6d075c)
• build(deps): Bump path-parse from 1.0.6 to 1.0.7 (#​425) (24f957e)
• feat: support @graphql-eslint/eslint-plugin out of box (#​413) (ec6fbb1)
• chore: add tests for Node 16 (#​410) (76bd45e)

v3.4.0

Compare Source

• feat: support processor virtual filename (#​401) (ee0ccc6)
• Simplify report logic (#​380) (d993f24)
• Update: README.md (#​375) (3ea4242)

---

Configuration

📅 Schedule: Branch creation - "on saturday" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.