You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
import/no-unresolved (at least for import statements, but not for require calls)
To avoid checking the same things the TypeScript compiler has already checked, I think it makes sense to also disable those rules (maybe except for import/no-unresolved) in the typescript config, so users don't have to (know and) disable them manually.
(It would also mitigate #2340 for TypeScript users.)
The text was updated successfully, but these errors were encountered:
The
typescript
config already disables theimport/named
rule because it does not have an advantage over errors thrown by the TypeScript compiler:eslint-plugin-import/config/typescript.js
Lines 31 to 32 in fa36d49
There are some more rules that fall in the same category, which also typescript-eslint recommends to disable:
import/namespace
import/default
import/no-named-as-default-member
import/no-unresolved
(at least forimport
statements, but not forrequire
calls)To avoid checking the same things the TypeScript compiler has already checked, I think it makes sense to also disable those rules (maybe except for
import/no-unresolved
) in thetypescript
config, so users don't have to (know and) disable them manually.(It would also mitigate #2340 for TypeScript users.)
The text was updated successfully, but these errors were encountered: