-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This plugin does not report import/extensions
and import/no-unresolved
errors on import type …
constructs
#3028
Comments
kmoschcau
changed the title
This plugin does not report any errors on
This plugin does not report Jul 14, 2024
import type …
constructsimport/extensions
and import/no-unresolved
errors on import type …
constructs
tsc itself would fail on those, no? |
No it does not. In fact it requires |
I can confirm 'no-restricted-syntax': ['error', {
selector: 'ImportDeclaration[importKind="type"][source.value=/^\\.\\.?\\x2F.+\\.js$/]',
message: 'Do not use ".js" file extension for relative import type declarations',
}], |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Assuming we force extensions
"always"
, I get the following results:This is not ideal, since I mostly deal with
.d.mts
files in the project where this occurs. And typescript enforcesimport type
on any.d.ts
and.d.mts
files.This is the
.eslintrc.cjs
of the project:The text was updated successfully, but these errors were encountered: