You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the flat config introduced in ESLint 8 and required as of ESLint 9 alpha, one has to import parsers and plugins. In so doing, TypeScript projects will be flagged with needing types for these packages.
Describe the solution you'd like
Types built into @babel/eslint-parser and @babel/eslint-plugin . This would avoid the need for a (potentially out of sync) Definitely Typed package.
Describe alternatives you've considered
Request a Definitely Typed package.
Documentation, Adoption, Migration Strategy
No response
The text was updated successfully, but these errors were encountered:
Hey @brettz9! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.
If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite.
馃捇
What problem are you trying to solve?
With the flat config introduced in ESLint 8 and required as of ESLint 9 alpha, one has to import parsers and plugins. In so doing, TypeScript projects will be flagged with needing types for these packages.
Describe the solution you'd like
Types built into @babel/eslint-parser and @babel/eslint-plugin . This would avoid the need for a (potentially out of sync) Definitely Typed package.
Describe alternatives you've considered
Request a Definitely Typed package.
Documentation, Adoption, Migration Strategy
No response
The text was updated successfully, but these errors were encountered: