False positive `no-undef` in TypeScript with interface

[kinyat]

see: eslint/typescript-eslint-parser#416

The problem with using StandardJS is that we do not have control on the rules thus we cannot turn off no-undef.

I hope we can add some config for TypeScript to turn this rule off.

Or allow user to turn off some of the rules.

[ColtonProvias]

It should be noted that abstract classes and class members inherited from abstract classes also throw this error.

[lukasoppermann]

Having the same issue, @feross is there a solution for this yet? Isn't there a way to specify configs for this somehow? Due to this issue I can't use standard anymore with typescript. Which sucks because standard is really awesome.

Please help.

Btw. a workaround is to add the interface to the globals in the files that use them:

/* global HTMLElement CustomEvent yourInterface */

[kevrat]

+1

[kevrat]

Also for no-use-before-define

[kinyat]

JYI: #1101

I have created a PR to turn this off for typescript but it hasn't been reviewed/approved and it is stale

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[mbret]

Any news on that ? The issue still exist and makes standardjs unusable with typescript.

[feross]

Let's track this issue here: #1283