Which project does this relate to?
Start
Describe the bug
The @tanstack/eslint-plugin-query and @tanstack/eslint-plugin-router packages have a peer dependency for eslint of "eslint": "^8.57.0 || ^9.0.0 || ^10.0.0" while the @tanstack/eslint-plugin-start package has "eslint": "^8.57.0 || ^9.0.0",.
Complete minimal reproducer
n/a
Steps to Reproduce the Bug
npm i -D eslint@v10.8.0
npm i -D @tanstack/eslint-plugin-query
npm i -D @tanstack/eslint-plugin-router
Now try
npm i -D @tanstack/eslint-plugin-start
Expected behavior
All eslint packages to have matching peer dependencies for eslint.
Screenshots or Videos
❯ npm i -D @tanstack/eslint-plugin-start
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: eslint-test@1.0.0
npm error Found: eslint@10.8.0
npm error node_modules/eslint
npm error dev eslint@"^10.8.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.57.0 || ^9.0.0" from @tanstack/eslint-plugin-start@0.1.0
npm error node_modules/@tanstack/eslint-plugin-start
npm error dev @tanstack/eslint-plugin-start@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
n
Platform
- Router Version: 1.170.18
- Start Version: 1.168.32
- OS: Windows
- Browser: n/a
- Browser Version: n/a
- Bundler: vite
- Bundler Version: 8.1.5
Additional context
No response
Which project does this relate to?
Start
Describe the bug
The
@tanstack/eslint-plugin-queryand@tanstack/eslint-plugin-routerpackages have a peer dependency for eslint of"eslint": "^8.57.0 || ^9.0.0 || ^10.0.0"while the@tanstack/eslint-plugin-startpackage has"eslint": "^8.57.0 || ^9.0.0",.Complete minimal reproducer
n/a
Steps to Reproduce the Bug
Now try
npm i -D @tanstack/eslint-plugin-startExpected behavior
All eslint packages to have matching peer dependencies for eslint.
Screenshots or Videos
Platform
Additional context
No response