Cannot find module '@typescript-eslint/parser' when using Prettier Eslint

Question

I'm getting the following error from Prettier Eslint Output on VSCode when saving the file.

Error: Cannot find module '@typescript-eslint/parser'
Require stack:
- c:\Users\vtnor\.vscode\extensions\rvest.vs-code-prettier-eslint-0.4.1\dist\extension.js
- c:\Program Files\Microsoft VS Code\resources\app\out\vs\loader.js
- c:\Program Files\Microsoft VS Code\resources\app\out\bootstrap-amd.js
- c:\Program Files\Microsoft VS Code\resources\app\out\bootstrap-fork.js

My package json is:

[...]
"typescript": "^4.2.2",
"@typescript-eslint/eslint-plugin": "^4.16.1",
"@typescript-eslint/parser": "^4.16.1",
"eslint": "^7.21.0",
"prettier": "^2.2.1",
"prettier-eslint": "^12.0.0",
[...]

bloo · Accepted Answer · 2021-03-03T02:19:18.300

11

i actually had this problem the other day ey, you need to go to your .eslintrc and make sure that the module is there under the parser property of the config...should look something like this in the end:

{
  //...

  "extends": [
    "eslint:recommended",
    "plugin:@typescript-eslint/eslint-recommended",
    "plugin:@typescript-eslint/recommended",
    "prettier/@typescript-eslint",
    "plugin:prettier/recommended"
  ],
  "parser": "@typescript-eslint/parser",
  "plugins": [
    "@typescript-eslint"
  ],

  //...
}

This should cover the essentials regarding dependencies in your linter...hope it helps

Edit

I checked git hub for this issue, might not be the same as the one I had, check this link please https://github.com/prettier/prettier-vscode/issues/905

edited Mar 03 '21 at 02:19

answered Mar 02 '21 at 18:15

bloo

1,416
2
13
19

I tried to add and remove this parser line. Currently I do have this line and I moved it - just in case - to be after extends. Still got the same error. – Vítor Norton Mar 02 '21 at 20:01
This isn't the same error, but I did try to restart my PC. Didn't work. – Vítor Norton Mar 03 '21 at 22:34
not working please let me know if you find any solution @VítorNorton – Amiya Panigrahi Aug 31 '21 at 10:42
Thank you, it worked for me. Make sure that you also restart vscode to see the warning disappear. – Bart Mar 19 '22 at 18:40

score 8 · Answer 2 · answered Sep 14 '21 at 08:46

8

Had this problem also, I resolved disabling, then reloading and re-enabling ESLint extension of VSCode.

Hope this helps ;)

answered Sep 14 '21 at 08:46

Claudio Bertozzi

536
4
12

score 3 · Answer 3 · answered Aug 09 '21 at 15:26

3

I discovered that the cause of the error in my case was ESLint itself was throwing an error. I discovered this by looking at the ESLint output in VSCode. The fix was to update one of my other dependencies (eslint-plugin-import).

answered Aug 09 '21 at 15:26

user15717674

51
1

score 2 · Answer 4 · answered Jun 21 '22 at 06:36

2

Open VS Code in the correct directory.

Example, we have:

/dir1/
/dir1/node_modules

In the dir1 directory
. Right click
. Open with Code

answered Jun 21 '22 at 06:36

Manohar Reddy Poreddy

25,399
9
157
140

score 1 · Answer 5 · answered May 31 '21 at 16:27

The problem probably that .eslintrc is not finding necessary modules because that are in a wrong location. .eslintrc needs to have folder node_modules right next to it. This can easily be achieved by putting .eslintrc into the project folder and creating package.json right next to it. Then node_modules will also be created in the project folder and the necessary (and installed) modules will be found.

Your project folder should look similar to:

score 1 · Answer 6 · answered Jan 28 '22 at 13:11

1

Installing @typescript-eslint/eslint-plugin and then reloading VSCode solved the issue for me.

Hope this helps anyone :D

answered Jan 28 '22 at 13:11

Deemo Harlos

19
1

score 1 · Answer 7 · answered Dec 21 '22 at 23:44

1

Fixed this with npm remove @typescript-eslint/parser && npm install @typescript-eslint/parser

answered Dec 21 '22 at 23:44

Max Pekarsky

590
2
6
20

score 0 · Answer 8 · answered Oct 15 '21 at 07:16

0

I just added the metro.config.js (like I did for an other fix for babel.config.js) to .eslintignore.

answered Oct 15 '21 at 07:16

Fotios Tsakiris

1,310
1
18
24

Cannot find module '@typescript-eslint/parser' when using Prettier Eslint

8 Answers8