Skip to content

build: update eslint-next-config to avoid npm install errors #781

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ianhi
Copy link
Contributor

@ianhi ianhi commented Jun 5, 2025

Prior to this change I was getting these errors when I would npm install

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: eslint-config-next@14.2.14
npm error Found: eslint@9.12.0
npm error node_modules/eslint
npm error   dev eslint@"^9.12.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/utils@8.8.0
npm error     node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"8.8.0" from @typescript-eslint/eslint-plugin@8.8.0
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         @typescript-eslint/eslint-plugin@"^5.4.2 || ^6.0.0 || ^7.0.0 || ^8.0.0" from eslint-config-next@14.2.14
npm error         node_modules/eslint-config-next
npm error       1 more (@typescript-eslint/type-utils)
npm error     @eslint-community/eslint-utils@"^4.2.0" from eslint@9.12.0
npm error   4 more (@typescript-eslint/eslint-plugin, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.23.0 || ^8.0.0" from eslint-config-next@14.2.14
npm error node_modules/eslint-config-next
npm error   dev eslint-config-next@"14.2.14" from the root project
npm error
npm error Conflicting peer dependency: eslint@8.57.1
npm error node_modules/eslint
npm error   peer eslint@"^7.23.0 || ^8.0.0" from eslint-config-next@14.2.14
npm error   node_modules/eslint-config-next
npm error     dev eslint-config-next@"14.2.14" 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 /Users/ian/.npm/_logs/2025-06-05T20_23_07_927Z-eresolve-report.txt
npm error A complete log of this run can be found in: /Users/ian/.npm/_logs/2025-06-05T20_23_07_927Z-debug-0.log

now we only get some npm warns about a few other packages

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: react-lorem-component@0.13.0
npm warn Found: react@18.3.1
npm warn node_modules/react
npm warn   react@"^18.3.1" from the root project
npm warn   31 more (@chakra-ui/color-mode, @chakra-ui/hooks, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer react@"16.x" from react-lorem-component@0.13.0
npm warn node_modules/react-lorem-component
npm warn   react-lorem-component@"^0.13.0" from @chakra-ui/react@2.9.1
npm warn   node_modules/@chakra-ui/react
npm warn
npm warn Conflicting peer dependency: react@16.14.0
npm warn node_modules/react
npm warn   peer react@"16.x" from react-lorem-component@0.13.0
npm warn   node_modules/react-lorem-component
npm warn     react-lorem-component@"^0.13.0" from @chakra-ui/react@2.9.1
npm warn     node_modules/@chakra-ui/react

Copy link

vercel bot commented Jun 5, 2025

@ianhi is attempting to deploy a commit to the xarray Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

netlify bot commented Jun 5, 2025

Deploy Preview for xarraydev failed.

Name Link
🔨 Latest commit 8410605
🔍 Latest deploy log https://app.netlify.com/projects/xarraydev/deploys/684200d67373d50008e103d9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant