Versions incompatible issue with eslint(9.9.1) & eslint-plugin-promise(7.1.0)

[GOPIKRISHNA11596]

Issue Description

• In my project, we are using "eslint", "eslint-config-standard", "eslint-plugin-promise" npm packages. When we update the eslint to latest version 9.9.1, we are getting below error,

npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: @ibm-app-connect/[email protected] npm ERR! Found: [email protected] npm ERR! node_modules/eslint npm ERR! dev eslint@"^9.9.1" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer eslint@"^8.0.1" from [email protected] npm ERR! node_modules/eslint-config-standard npm ERR! dev eslint-config-standard@"^17.1.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.

• Same is happening for eslint-plugin-promise for version 7.1.0,

npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: @ibm-app-connect/[email protected] npm ERR! Found: [email protected] npm ERR! node_modules/eslint-plugin-promise npm ERR! dev eslint-plugin-promise@"^7.1.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer eslint-plugin-promise@"^6.0.0" from [email protected] npm ERR! node_modules/eslint-config-standard npm ERR! dev eslint-config-standard@"^17.1.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.

• eslint-config-standard is not compatible with latest the versions of eslint & eslint-plugin-promise. I have done some analysyis and added screenshot. Even the latest version of eslint-config-standard is pointing to old versions of eslint & eslint-plugin-promise. Please help us on this.

[alexey-sh]

How is it going?

[amberlionk]

is there a chance this would be fixed?

[voxpelli]

It's fixed in https://github.com/neostandard/neostandard