-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
default eslint-config-next version has peer conflicts causing npm installs to fail #30536
Closed
1 of 4 tasks
Labels
Comments
DB-db-dron
added a commit
to DB-db-dron/nx
that referenced
this issue
Mar 28, 2025
ndcunningham
pushed a commit
that referenced
this issue
Mar 31, 2025
ndcunningham
added a commit
that referenced
this issue
Mar 31, 2025
Closes #30536 <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior The current version of eslint-config-next (v14.2.16) has peer dependency conflicts with the latest versions of ESLint (v9.x). This issue causes npm install to fail in projects using eslint-config-next. ## Expected Behavior `npm install` should succeed without dependency conflicts. ## Related Issue(s) Fixes #30536 --------- Co-authored-by: Nicholas Cunningham <[email protected]>
jaysoo
pushed a commit
that referenced
this issue
Apr 2, 2025
Closes #30536 <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior The current version of eslint-config-next (v14.2.16) has peer dependency conflicts with the latest versions of ESLint (v9.x). This issue causes npm install to fail in projects using eslint-config-next. ## Expected Behavior `npm install` should succeed without dependency conflicts. ## Related Issue(s) Fixes #30536 --------- Co-authored-by: Nicholas Cunningham <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
The current version of eslint-config-next (v14.2.16) has peer dependency conflicts with the latest versions of ESLint (v9.x). This issue causes npm install to fail in projects using eslint-config-next.
Expected Behavior
npm install
should succeed without dependency conflicts.GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: