Next.js Discord

Discord Forum

eslint-config-next@14.2.3 dependency conflict

Answered
Black Caiman posted this in #help-forum
Open in Discord
Black CaimanOP
I'm trying to deploy my recent changes to Vercel but I'm struggling to fix some dependency conflicts. I've also attached my packages from my package.json file.

After a couple of months, I've recently made some changes to my portfolio site and had to update most packages.

Within the terminal (local), I faced some dependency conflicts which I later resolved with the --legacy-peer-deps flag. I had no issues and nothing shows when I run npm outdated.

After creating a pull request, I see the attached error during the build process. It's my first time dealing with this and I'm not sure how to fix this. Any help would be appreciated!
Answered by joulev
eslint-config-next is not compatible with eslint v9 so keep it at v8 at most
View full answer

15 Replies

Answer
@joulev eslint-config-next is not compatible with eslint v9 so keep it at v8 at most
Black CaimanOP
ah right! How am i supposed to find the right v8.x.x version for eslint-config-next? 😕

Sorry, I'm so new to this
the latest 8.x.x perhaps
lemme check
8.57.0
Black CaimanOP
Thanks, trying it out
Black CaimanOP
PERFECT!!
The changes are now deployed
Thanks so much for your help @joulev ! 🙂 🏆
you're welcome
Black CaimanOP
For future reference, how can I check compatible dependencies and their version number?

The NPM site shows the dependencies but not the compatible one for the depending package.
F.Y.I I'm a junior dev in the making
@Black Caiman For future reference, how can I check compatible dependencies and their version number? The NPM site shows the dependencies but not the compatible one for the depending package.
this particular issue is pretty common in this server so i already knew so could instantly tell you, but from the error message you can see
peer eslint@"^7.23.0 || ^8.0.0" from eslint-config-next@14.2.3
meaning eslint-config-next@14.2.3 only accepts eslint v8 and eslint v7.23+. so eslint v9 is not accepted, causing a conflict
Black CaimanOP
Oh right, I see. So from there I assume it's a matter of tracing the latest v8 version close to v9 right?
Yep