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
Would be cool if *.ts were magically parsed by a (the?) TypeScript parser, such that JavaScript files that import from TypeScript could be properly linted.
Use case: transitioning from one to the other in a Webpack project, where loaders allow both to exist.
Possible general config option: import/parsers that maps from regexes to parser modules. Non-matches would continue to use the ESLint parser.
Could theoretically lint CoffeeScript or whatever else, assuming some module spit out a roughly ESTree-compatible AST (i.e. it has compatible export nodes in a Programbody).
The text was updated successfully, but these errors were encountered:
Would be cool if
*.ts
were magically parsed by a (the?) TypeScript parser, such that JavaScript files that import from TypeScript could be properly linted.Use case: transitioning from one to the other in a Webpack project, where loaders allow both to exist.
Possible general config option:
import/parsers
that maps from regexes to parser modules. Non-matches would continue to use the ESLint parser.Could theoretically lint CoffeeScript or whatever else, assuming some module spit out a roughly ESTree-compatible AST (i.e. it has compatible export nodes in a
Program
body
).The text was updated successfully, but these errors were encountered: