Failed to load plugin '@next/next' declared in '.eslintrc.js'

[aafnnp]

error - ESLint: Failed to load plugin '@next/next' declared in '.eslintrc.js': Unexpected token '.' Referenced from: 
info  - Creating an optimized production build...
warn  - Found lockfile missing swc dependencies, run next locally to automatically patch

[icyJoseph]

mmm what is @next/next? the next plugin is called eslint-config-next, and we typically extend next/core-web-vitals in the eslint config.

Would you mind sharing more? package.json and .eslintrc.js, also file structure if possible.

[aafnnp]

thx

[icyJoseph]

Aha! What node version did you have before? 14? It must have been new syntax... Good catch!

[aafnnp]

yes.14

[icyJoseph]

Alright, please comment what you did on a separate reply and label it is as answered! Good job!

[h0lme3]

Knew something new!

[mgouault]

Had the same error

yarn run v1.22.17
$ next lint
Failed to load plugin '@next/next' declared in '.eslintrc.json » eslint-config-next/core-web-vitals » /Users/mgouault/website/node_modules/eslint-config-next/index.js': Unexpected token '.'
Referenced from: /Users/mgouault/website/node_modules/eslint-config-next/index.js
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Upgraded from node 12.22 to node 14.19 then reinstalled node_modules and it works

[stefaneidelloth]

Thank you. That solved the issue for me, too. Also see https://stackoverflow.com/questions/73036716/failed-to-load-plugin-next-next-when-running-npm-run-lint-in-gitlab-ci/73063116#73063116

[nimeshmaharjan1]

I am getting this error in neovim prettier is working fine. I am using null-ls. This is just a starter template from pnpx create-next-app -ts-

and this is the eslintrc.json file

[medromo]

Hi, were you able to fix this issue? Im having the same problem

[sjdonado]

I fixed it by using these versions:

    "eslint-config-next": "^12.1.0",
    "eslint-plugin-react": "^7.28.0",
    "eslint-plugin-react-hooks": "^4.3.0",

then I restarted the eslint daemon eslint_d restart

[Nhahan]

this worked for me 😄

[nimeshmaharjan1]

Degrade next version I'm just using the pages for now bc the app gives me so many errors and don't even know from where and why

…

On Fri, 26 May 2023, 11:15 pm Rolando Medina, ***@***.***> wrote: Hi, were you able to fix this issue? Im having the same problem — Reply to this email directly, view it on GitHub <#38220 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUXM4BXQBWETK4BQRY5HNZTXIDSERANCNFSM52LHGBAQ> . You are receiving this because you commented.Message ID: <vercel/next. ***@***.***>

[medromo]

Thanks, I appreciate the response

[nanxiaobei]

it's @next/eslint-plugin-next.

pnpm add @next/eslint-plugin-next -D fixed it

[Robert-Sen]

thx, that works for me

[Tordek]

In my case this was caused by two versions of typescript being installed in a monorepo project. The root version was 4.x and the child was 5.x. Manually installing typescript@^5.0.0 in the base project fixed the issue.