Upgrade eslint-config to @wordpress/eslint-plugin 14

[orballo]

Is your enhancement related to a problem? Please describe.

npm install fails after upgrading @wordpress/eslint-plugin to v14.

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @10up/eslint-config@3.1.1
npm ERR! Found: @wordpress/eslint-plugin@14.11.0
npm ERR! node_modules/@wordpress/eslint-plugin
npm ERR!   dev @wordpress/eslint-plugin@"^14.11.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @wordpress/eslint-plugin@"^13.10.0" from @10up/eslint-config@3.1.1
npm ERR! node_modules/@10up/eslint-config
npm ERR!   peer @10up/eslint-config@"^3.1.1" from 10up-toolkit@5.2.2
npm ERR!   node_modules/10up-toolkit
npm ERR!     dev 10up-toolkit@"^5.2.2" from the root project
npm ERR!     1 more (10up-experience)
npm ERR!
npm ERR! Conflicting peer dependency: @wordpress/eslint-plugin@13.10.3
npm ERR! node_modules/@wordpress/eslint-plugin
npm ERR!   peerOptional @wordpress/eslint-plugin@"^13.10.0" from @10up/eslint-config@3.1.1
npm ERR!   node_modules/@10up/eslint-config
npm ERR!     peer @10up/eslint-config@"^3.1.1" from 10up-toolkit@5.2.2
npm ERR!     node_modules/10up-toolkit
npm ERR!       dev 10up-toolkit@"^5.2.2" from the root project
npm ERR!       1 more (10up-experience)
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.

Designs

No response

Describe alternatives you've considered

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[orballo]

Actually, this shouldn't fail because usually you don't need to install @wordpress/esling-plugin on your own.

[nicholasio]

In the latest version of toolkit you shouldn't need to update this (or include this manually). We'll bump this package in the next major.

[nicholasio]

Updated in #350