Bug: Cannot be installed alongside recent versions of `svelte-eslint-parser`

[Stadly]

Describe the bug

When I install eslint-plugin-perfectionist, I get the following error, since I have a version of svelte-eslint-parser that is newer than 0.33.1. I don't expect there to be any incompatibilities, but it seems the peer-dependency settings of eslint-plugin-perfectionist prevents installation alongside recent versions of svelte-eslint-parser.

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: midlaier@0.1.0
npm error Found: svelte-eslint-parser@0.34.0
npm error node_modules/svelte-eslint-parser
npm error   svelte-eslint-parser@">=0.34.0 <1.0.0" from eslint-plugin-svelte@2.37.0
npm error   node_modules/eslint-plugin-svelte
npm error     dev eslint-plugin-svelte@"^2.37.0" from the root project
npm error
npm error Could not resolve dependency:
npm error dev eslint-plugin-perfectionist@"*" from the root project
npm error
npm error Conflicting peer dependency: svelte-eslint-parser@0.33.1
npm error node_modules/svelte-eslint-parser
npm error   peerOptional svelte-eslint-parser@"^0.33.0" from eslint-plugin-perfectionist@2.10.0
npm error   node_modules/eslint-plugin-perfectionist
npm error     dev eslint-plugin-perfectionist@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /root/.npm/_logs/2024-06-05T09_29_20_646Z-eresolve-report.txt

npm error A complete log of this run can be found in: /root/.npm/_logs/2024-06-05T09_29_20_646Z-debug-0.log

Code example

npm install --save-dev eslint-plugin-perfectionist

ESLint version

v8.57.0

ESLint Plugin Perfectionist version

v2.10.0

Additional comments

No response

Validations

• [X] Read the docs.
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

[azat-io]

Looks like problem was fixed in #149