Update dependency eslint-config-prettier to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-config-prettier	^8.5.0 -> ^10.0.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

prettier/eslint-config-prettier (eslint-config-prettier)

v10.1.8

Compare Source

republish latest version

Full Changelog: prettier/eslint-config-prettier@v10.1.5...v10.1.8

v10.1.5

Compare Source

Patch Changes

• #​332 60fef02 Thanks @​JounQin! - chore: add funding field into package.json

v10.1.4

Compare Source

Patch Changes

• #​328 94b4799 Thanks @​silvenon! - fix(cli): do not crash on no rules configured

v10.1.3

Compare Source

Patch Changes

• #​325 4e95a1d Thanks @​pilikan! - fix: this package is commonjs, align its types correctly

v10.1.2

Compare Source

Patch Changes

• #​321 a8768bf Thanks @​Fdawgs! - chore(package): add homepage for some 3rd-party registry - see #​321 for more details

v10.1.1

Compare Source

Patch Changes

• #​309 eb56a5e Thanks @​JounQin! - fix: separate the /flat entry for compatibility

  For flat config users, the previous "eslint-config-prettier" entry still works, but "eslint-config-prettier/flat" adds a new name property for config-inspector, we just can't add it for the default entry for compatibility.

  See also #​308

  // before
  import eslintConfigPrettier from "eslint-config-prettier";
  
  // after
  import eslintConfigPrettier from "eslint-config-prettier/flat";

v10.1.0

Compare Source

Minor Changes

• #​306 56e2e34 Thanks @​JounQin! - feat: migrate to exports field

v10.0.3

Compare Source

Patch Changes

• #​294 8dbbd6d Thanks @​FloEdelmann! - feat: add name to config

• #​280 cba5737 Thanks @​zanminkian! - feat: add declaration file

v10.0.2

Compare Source

Patch Changes

• #​299 e750edc Thanks @​Fdawgs! - chore(package): explicitly declare js module type

v10.0.1

Compare Source

eslint-config-prettier

10.0.1

What's Changed

• chore: migrate to changeset for automatically releasing by @​JounQin in #​278
• add support for @stylistic/eslint-plugin by @​abrahamguo in #​272

New Contributors

• @​JounQin made their first contribution in #​278
• @​abrahamguo made their first contribution in #​272

Full Changelog: prettier/eslint-config-prettier@v9.1.0...v10.0.1

v10.0.0

Compare Source

Major Changes

• #​272 5be64be Thanks @​abrahamguo! - add support for @​stylistic formatting rules

v9.1.2

Compare Source

v9.1.0

Compare Source

• Added: [unicorn/template-indent], (as a [special rule][unicorn/template-indent-special]). Thanks to Gürgün Dayıoğlu (@​gurgunday)!
• Changed: All the [formatting rules that were deprecated in ESLint 8.53.0][deprecated-8.53.0] are now excluded if you set the ESLINT_CONFIG_PRETTIER_NO_DEPRECATED environment variable.

v9.0.0

Compare Source

• Added: The CLI helper tool now works with eslint.config.js (flat config). Just like ESLint itself, the CLI tool automatically first tries eslint.config.js and then eslintrc, and you can force which one to use by setting the [ESLINT_USE_FLAT_CONFIG] environment variable. Note that the config of eslint-config-prettier has always been compatible with eslint.config.js (flat config) – it was just the CLI tool that needed updating. On top of that, the docs have been updated to mention how to use both eslint.config.js (flat config) and eslintrc, and the tests now test both config systems.
• Changed: [unicode-bom] is no longer turned off. Prettier preserves the BOM if you have one, and does not add one if missing. It was wrong of eslint-config-prettier to disable that rule. If you get ESLint errors after upgrading, either add "unicode-bom": "off" to your config to disable it again, or run ESLint with --fix to fix all files according to the rule (add or remove BOM). Thanks to Nicolas Stepien (@​nstepien)!

v8.10.2

Compare Source

v8.10.0

Compare Source

• Added: [max-statements-per-line]. Thanks to @​Zamiell!

v8.9.0

Compare Source

• Added: [vue/array-element-newline]. Thanks to @​xcatliu!

v8.8.0

Compare Source

• Added: [@​typescript-eslint/lines-around-comment]. Thanks to @​ttionya!

v8.7.0

Compare Source

• Added: [@​typescript-eslint/block-spacing]. Thanks to @​ttionya!
• Added: [@​typescript-eslint/key-spacing]. Thanks to @​ttionya!

v8.6.0

Compare Source

• Added: [vue/multiline-ternary]. Thanks to @​xcatliu!

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: flink-runtime-web/web-dashboard/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/zone.js
npm ERR!   zone.js@"0.15.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.11.4" from @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"13.4.0" from the root project
npm ERR!   peer @angular/core@"13.4.0" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"13.4.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-10-23T10_17_34_985Z-debug-0.log