-
-
Notifications
You must be signed in to change notification settings - Fork 166
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
[feature request]: functional resolvePackage
option/setting support
#186
Comments
In my understanding, when we install So |
@mysticatea We may only import types of And also, unist (404) |
Ah, I got it. |
This enhancement needs design because ESLint doesn't support function type in rule options. |
@mysticatea Is it possible to integrate with the resolvers for https://github.com/alexgorbatchev/eslint-import-resolver-typescript This resolver could help, or we can simply wrap it. |
Motivation: I'm always using
TypeScript
personally, for most packages we can use following settings:But it won't work for scoped packages like
@babel/core
, its typed definition is under@types/babel__core
directory, soresolvePaths
will not work for it. Of course, we can useallowModules
for workaround, but it could be a mistake if we forget to install the@types/babel__core
module.The text was updated successfully, but these errors were encountered: