Skip to content
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.

Sign up for GitHub

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

Jump to bottom

import/no-unresolved can't resolve module under node_modules/@types #1695

Closed
tjx666 opened this issue Mar 24, 2020 · 3 comments
Closed

import/no-unresolved can't resolve module under node_modules/@types #1695

tjx666 opened this issue Mar 24, 2020 · 3 comments

Comments

@tjx666
Copy link

tjx666 commented Mar 24, 2020

screenshot_2020-03-24_10-09-21

versions:

"eslint": "^6.8.0",
"eslint-import-resolver-typescript": "^2.0.0",
"eslint-plugin-import": "2.20.1",
"typescript": "^3.8.3",
"@typescript-eslint/eslint-plugin": "^2.25.0",
"@typescript-eslint/parser": "^2.25.0",
@tjx666 tjx666 changed the title import/no-unresolved can't recogonize module under node_modules/@types import/no-unresolved can't resolve module under node_modules/@types Mar 24, 2020
@ljharb
Copy link
Member

ljharb commented Mar 24, 2020 •
edited

Your image points to @types/html-minifier, not html-minifier. Is the latter present?

@tjx666
Copy link
Author

tjx666 commented Mar 24, 2020

@ljharb not existed，but I didn't have this problem before. If I using @types/html-minifier, tsc will throw another error:

screenshot_2020-03-24_10-34-32

@ljharb
Copy link
Member

ljharb commented Mar 24, 2020

ah, i think this is a duplicate of #1618?

@ljharb ljharb closed this as completed Mar 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ljharb @tjx666