We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
By default, ESLint only looks at files with the .js extension. However, after installing this plugin, this override causes it to lint .ts files too.
.js
.ts
Since I am in a JS codebase with a manually written .d.ts file, I get parsing errors like this:
.d.ts
12:9 error Parsing error: Unexpected token const
on
index.d.ts
declare const myFunction: (name: string) => Promise<boolean>;
I would prefer it doesn't try to lint my .d.ts or ts files if I don't have the Typescript plugin installed.
ts
Although there are workarounds for this, I think this is unexpected default behavior that shouldn't require patching on user-land.
Workarounds:
"ignorePatterns": ["*.ts"]
The text was updated successfully, but these errors were encountered:
require-post-message-target-origin
Successfully merging a pull request may close this issue.
By default, ESLint only looks at files with the
.js
extension. However, after installing this plugin, this override causes it to lint.ts
files too.Since I am in a JS codebase with a manually written
.d.ts
file, I get parsing errors like this:on
index.d.ts
I would prefer it doesn't try to lint my
.d.ts
orts
files if I don't have the Typescript plugin installed.Although there are workarounds for this, I think this is unexpected default behavior that shouldn't require patching on user-land.
Workarounds:
"ignorePatterns": ["*.ts"]
The text was updated successfully, but these errors were encountered: