Closed charlie632 closed 1 year ago
Could you try setting the tsconfigRootDir
as indicated in the typescript-eslint docs?
The crash occurs because of an out of memory exception. In general the heap in Node is limited to 4GB and depending on the Electron version used in VS Code this can't be increased (https://github.com/electron/electron/issues/31330). What you can do to lift the memory is:
eslint.runtime
setting to point to iteslint.argv
to increase the heap size used by node to lift the 4GB to for example 8GB.@MariaSolOs upgrading to
"@typescript-eslint/eslint-plugin": "^5.60.1",
"@typescript-eslint/parser": "^5.60.1",
and following the docs did it!
Thanks.
@charlie632 glad you made it work! Setting up typescript-eslint
can be really tricky sometimes...
@MariaSolOs yeah, it is ☹️! Thanks for the help!
I'm trying to use a couple of ESlint rules that required me to pass
parserOptions.project
to the ESlint config. Whenever I add that option to ESLint, the server automatically crashes, but when I comment theparserOptions
object, it works as expected.As additional notes, I can run ESLint without any issue via CLI, this is only happening in the VSCode Extension Server.
Libs:
@typescript-eslint/parser@5.50.0
eslint@8.32.0
This is the ESLint config inside the package:
and this is the ESLint at the root of the monorepo
and the
tsconfig.json
VSCode Eslint Server Output