-
-
Notifications
You must be signed in to change notification settings - Fork 64
Issues: import-js/eslint-import-resolver-typescript
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
Author
Label
Milestones
Assignee
Sort
Issues list
[Question] Required with new typescript eslint plugin and eslint 9?
#310
opened Aug 15, 2024 by
SalahAdDin
Imports with tsconfig paths and .js extension to .tsx importee don’t resolve
#292
opened Jun 20, 2024 by
davidensinger
import/extensions
, import/no-unresolved
don't highlight import of nonexistent .js
#291
opened Jun 16, 2024 by
jwbth
Support for
project: true
or useProjectService: true
?
help wanted
#282
opened May 1, 2024 by
Samuel-Therrien-Beslogic
eslint-plugin-x
's old name eslint-plugin-i
is still used in docs
#281
opened May 1, 2024 by
Samuel-Therrien-Beslogic
Missing file extension "ts" for [...] / passing through
enhanced-resolve
's options.
#233
opened Jul 9, 2023 by
Patryk-B
Support declaring internal module regex or respect import/internal-regex setting
#227
opened May 24, 2023 by
harunurhan
import/no-unresolved: wildcard exports causing import resolution error in a monorepo
#218
opened Mar 24, 2023 by
davbrito
import/no-unused-modules conflicts with typescript moduleSuffixes
#211
opened Jan 31, 2023 by
nzaytsev
[import/no-unresolved] when importing from another package in a monorepo
#210
opened Jan 30, 2023 by
tpluscode
Call to
enhanced-resolve
converts #
in paths to \0#
, which crashes eslint-plugin-import
#208
opened Jan 15, 2023 by
ashmind
Adapt
get-tsconfig
's TsConfigJsonResolved
to TypeScript's ParsedCommandLine
#179
opened Sep 2, 2022 by
JounQin
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.