-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
types of @typescript-eslint/eslint-plugin
are not published
#3129
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
We don't publish them on purpose because there is little use to them - they are only useful specifically in the case where you are extending our rules (which is literally maybe used by 0.00000001% of our users). Additionally turning on type declarations for the package is a pain as it causes TS to enforce requirements about private types - meaning files have to export extra cruft. |
How about add a minimal declaration file? My temporary workaround: declare module '@typescript-eslint/eslint-plugin' {
import { Rule } from 'eslint'
export const rules: Record<string, Rule.RuleModule>
// configs can be exported too
} |
we purposely don't have any dependency on the ESLint types as they are wrong with respect to our project, so they would have to use the types from our packages. |
So should I PR to this repo or DefinitelyTyped instead? |
Feel free to PR it here! |
Repro
https://unpkg.com/browse/@typescript-eslint/eslint-plugin@4.16.1/
Expected Result
Actual Result
Additional Info
Versions
@typescript-eslint/eslint-plugin
4.15.2
@typescript-eslint/parser
4.15.2
TypeScript
4.1.3
The text was updated successfully, but these errors were encountered: