Error: Cannot calculate TypeScript semantic issues without a valid project about eslint-plugin-import HOT 11 CLOSED

Hard to say much of anything without some information. Would need a repro to be able to provide any advice.

Though the reported error message isn't one of ours.

from eslint-plugin-import.

We don't yet support v6 of the TS eslint parser (meaning, we don't test on it).

from eslint-plugin-import.

Do you have any plans?

from eslint-plugin-import.

I believe @bradzacher is more suitable to answer the question.

from eslint-plugin-import.

I suspect this error comes from tsconfig-paths; it’s not one of ours either.

from eslint-plugin-import.

Reproduce repo
This is a cleaned up version of our config.
Before the update to typescript-eslint/parser@6, everything worked fine.

If I comment these lines eslint-module-utils/parser.js

  delete parserOptions.EXPERIMENTAL_useProjectService;
  delete parserOptions.project;
  delete parserOptions.projects;

Everything also worked fine.

from eslint-plugin-import.

To fix this, we'll need to start testing on v6 of the TS eslint parser.

from eslint-plugin-import.

errorOnTypeScriptSyntacticAndSemanticIssues: true,

I had forgotten that even existed. I didn't know people used it - it's literally tge first time I've ever seen it used.

Turn that off and it'll work.

from eslint-plugin-import.

This is a common standard for our company, I'll ask if we can disable it.

But in any case, do you think this is normal behavior?

from eslint-plugin-import.

Yes. The behaviour of deleting the parser options is intended (and implemented by me).
eslint-plugin-import does its own out-of-band parsing so it can analyse exports of dependencies. To do this is uses your configured parser.

If we leave those parser options behind then it means that when import/ attempts to parse a dependency it will cause our parser to attempt to do a type-aware parse. If the file isn't part of a project (eg it's in node_modules) then this causes REALLY REALLY REALLY BAD BEHAVIOUR such as crashes or CRAZY BAD slowness (as you noted - #1408)

When I added those deletes 5 years ago I didn't remember errorOnTypeScriptSyntacticAndSemanticIssues existed.
In v6 we changed the underlying infra so that that option requires type information.

It's an undocumented parser option and shouldn't actually work within eslint anyways. We'll look at removing it entirely (filed typescript-eslint/typescript-eslint#8681).

You should delete it from your eslint config.

from eslint-plugin-import.

Got it, thanks!

from eslint-plugin-import.