Open artaommahe opened 2 months ago
if they're types, is there a reason you can't use import type
?
using import type
helps, but it requires to do this manually. By default vscode add auto-imports without type
. It's not a good idea to force developers manually check imports list and add type
to random places (and frequently imports list is just collapsed by default).
I agree, and we do need a lint rule for that (#2390).
In the meantime, let's figure this out. Can you confirm you're using the latest version of the TS resolver?
This "rule change" seems to be very inconsistent, as it seems to only trigger on external dependencies, at least in our project. Any internal types and interfaces imported as "import { SomeType } from "./someInterface"" are not affected.
We would very much like to keep using our old importing style, and would appreciate if this, if not a bug, could be configured. This issue seems to happen after upgrading "eslint-module-utils" to version"2.9.0" or above. Our temporary solution has been to pin both "eslint-module-utils" and "eslint-plugin-import" to "2.8.2" and "2.29.0" respectively.
@ljharb what's ts resolver?) just in case "typescript": "5.5.4",
@artaommahe eslint-import-resolver-typescript - it’s required to be able to lint typescript files properly with this plugin; see the readme.
@ljharb eslint-import-resolver-typescript@3.6.3
any updates?
After upgrading from 2.29.1 to 2.30.0 we got some
not found
errors fromimport/named
rulein both cases only imported interfaces are marked with error