chore(deps): update dependency eslint-plugin-prettier to v5
This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| eslint-plugin-prettier | ^4.0.0 -> ^5.0.0 |
Release Notes
prettier/eslint-plugin-prettier (eslint-plugin-prettier)
v5.5.4
Patch Changes
-
#755
723f7a8Thanks @kbrilla! - fix: add 'oxc', 'oxc-ts' and 'hermes' parsers toparserBlocklist -
#751
cf52b30Thanks @andreww2012! - fix: disallow extra properties in rule options
v5.5.3
republish the latest version
Full Changelog: https://github.com/prettier/eslint-plugin-prettier/compare/v5.5.2...v5.5.3
v5.5.2
republish the latest version
Full Changelog: https://github.com/prettier/eslint-plugin-prettier/compare/v5.5.1...v5.5.2
v5.5.1
Patch Changes
v5.5.0
Minor Changes
- #743
92f2c9cThanks @dotcarmen! - feat: support non-js languages likecssfor@eslint/cssandjsonfor@eslint/json
v5.4.1
Patch Changes
- #740
c21521fThanks @JounQin! - fix(deps): bumpsynckitto v0.11.7 to fix potentialTypeError: Cannot read properties of undefined (reading 'message')error
v5.4.0
Minor Changes
- #736
59a0caeThanks @yashtech00! - refactor: migrateworker.jstoworker.mjs
v5.3.1
Patch Changes
v5.3.0
Minor Changes
v5.2.6
Patch Changes
- #723
1451176Thanks @renovate! - fix(deps): bumpsynckittov0.11.0
v5.2.5
Patch Changes
v5.2.4
Patch Changes
v5.2.3
Patch Changes
v5.2.2
Patch Changes
v5.2.1
Patch Changes
- #668
ac036ccThanks @OrlovAlexei! - build(deps): Bump synckit from 0.8.6 to 0.9.1
v5.1.3
Patch Changes
v5.1.2
Patch Changes
-
#623
8210e44Thanks @BPScott! - Add exports mapping to package.json, to allowimport 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
2b09e7fThanks @JounQin! - feat: support parsingmarkdownviaeslint-mdxnativelyWhat 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
Patch Changes
v5.1.0
Minor Changes
-
#616
3856413Thanks @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 ofeslint-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
5270877Thanks @BPScott! - Add meta block to plugin. This improves debugging and cachebusting when using the new flat config -
#603
a63a570Thanks @filiptammergard! - fix: specifyeslint-config-prettieras peer dependencyIt's already added to
peerDependenciesMetaas optional, which means it should also be specified inpeerDependencies.
v5.0.1
Patch Changes
- #588
21a7146Thanks @krist7599555! - fix:parserPathtype might beundefinedon Eslint Falt Config
v5.0.0
Major Changes
-
#508
910aeb6Thanks @JounQin! - feat!: bump peer eslint to ">=8.0.0" and node to "^14.18.0 || >=16.0.0" -
#508
910aeb6Thanks @JounQin! - feat!: upgrade to prettier v3
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.
/gcbrun
Summary of Changes
Hello @renovate-bot, I'm Gemini Code Assist[^1]! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request updates the eslint-plugin-prettier development dependency to its latest major version. This ensures the project benefits from the newest features, performance improvements, and bug fixes provided by the plugin, aligning the codebase with modern linting and formatting standards.
Highlights
- Dependency Update: The
eslint-plugin-prettierdependency has been updated to its major version5.x.x. - Compatibility Requirements: This major version upgrade requires
ESLint >=8.0.0andNode.js >=14.18.0 || >=16.0.0, and is compatible withPrettier v3. - New Features: Version 5 introduces support for non-JavaScript languages (e.g., CSS, JSON) and adds a recommended configuration for ESLint's new flat config format.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in pull request comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
[^1]: Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.