ESLint randomly started enforcing new rule which is incorrect and breaking my builds

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Node version: v16.15.1 npm version: 8.19.0 Local ESLint version: 8.23.0 Global ESLint version: N/A Operating System: macOS Big Sur / M1 Mac

What browser are you using? (if relevant)

N/A

How are you deploying your application? (if relevant)

Vercel

Describe the Bug

ESLint is enforcing a rule which is breaking my build.

File	Vercel Build Error

I went through my old vercel builds and found where it stopped working—I updated some packages and that was it. I just tried to revert back to all the old package versions where the builds were working fine and I still am getting the errors now.

I’m not sure why ESLint decided to enforce this rule randomly or why it’s throwing an error even though it’s a real property. I know I can ignore it with next.js configs but I’m instead trying to figure out what’s happening here.

I also have an identical personal portfolio project with the same setup code and up-to-date packages in which I’m not having this issue. I can’t understand why it’s only happening on this repo.

If you have any ideas as to what’s happening please let me know, thank you.

I have made an issue over at ESLint’s repo too as I’m not sure which would be more appropriate.

Expected Behavior

Builds should pass.

Link to reproduction

https://github.com/tr1s/nightizm

To Reproduce

Run npm run lint and see that these errors are showing up. They shouldn’t be showing up at all.

[JDansercoer]

@ljharb this shouldn’t be closed, as eslint-plugin-react is a dependency of eslint-config-next and is currently not a direct dependency of our project. Next should update the version range to not include the broken dependency.

[tr1s]

yeah @JDansercoer @ljharb looks like esling-config-next is using the old version of eslint-plugin-react:

I will keep the issue open until my eslint-config-next get’s updated. It’s currently 12.2.5 and 12.2.6 is in canary still (assuming this update will have the correctly updated package).