-
-
Notifications
You must be signed in to change notification settings - Fork 69
[BUG] import/no-unresolved error despite correct 'declare module' and TypeScript resolution #224
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
Comments
I am facing this issue too. Just checking this thread if we have any resolution till now. |
Update: I was able to resolve this issue. I messed up by tsconfig.json and due to this my dist folder of the imported package, doesn't have the index.ts file generated. |
I am facing a similar issue as reported by tzachbon. If you can prioritize fixing this issue, I would really appreciate your effort. Issue: eslintrc: module: tsconfig: |
Bump! Same thing. Perhaps #197 should be closed in favor of this issue for tracking? |
Yes, same thing, so close due to duplicate. |
I'm encountering errors related to resolving the path of a custom request.
The TypeScript compiler can resolve these paths without any issues, thanks to the correct declare module statement in a
d.ts
file:Despite the declared module statement, Eslint still throws import/no-unresolved errors for the
accProjectList/*
modules.Expected Behavior
The plugin should recognize the declared module statement and be able to resolve the paths to the
accProjectList/*
modules without any errors, just as TypeScript does.Additional Information
Eslint version: v8.36.0
eslint-import-resolver-typescript version: 3.5.5
TypeScript version: Version 5.0.2
Node.js version: v18.14.0
Operating System: arm64
.eslintrc
:Any help or guidance on resolving this issue and ensuring Eslint correctly recognizes the declaration module statement would be greatly appreciated. Thank you!
The text was updated successfully, but these errors were encountered: