TSInterfaceDeclaration by itself doesn't trigger a semi check purely because it doesn't match the base rule's matchers.

https://github.com/eslint/eslint/blob/faf3c4eda0d27323630d0bc103a99dd0ecffe842/lib/rules/semi.js#L320-L324

The base rule has a specific case for ExportDefaultDeclaration, and only skips the semi check if it's a class or function declaration.

We might have to override the rule for this one.

Temp workaround is to define your interface separately:

interface Foo {}
export default Foo;

@bradzacher could this possibly be fixed in eslint by making the ExportDefaultDeclaration check use a whitelist instead of a blacklist?

Probably would fix it, but the problem is:

• there is a large number of nodes that would need to be whitelisted
• it would cause false positives as new language features get supported by the base ESTree representation

We can bring this rule internally and extend its so that it works for TS nodes.

I don't suppose this is related to eslint/eslint#9399 is it?

I'm seeing it in my app too.

export default interface AudioFactory{
    getSong(id: string): Promise<Song>;
};

I get missing semicolon

Fixed by #461

Fixed by #461

I've tried:

• "@typescript-eslint/semi": "error"
• "@typescript-eslint/semi": "[2, "always"]"

Unfortunately, none of which work. Is something missing?

https://github.com/typescript-eslint/typescript-eslint/releases

Hasn't been released to master yet.
Try the canary tag on npm for builds directly from master if you don't want to wait for a main release.

@bradzacher tried 1.7.1-alpha.16, marked as canary, but I still have the same problem

@bjerkins - you still have the base semi rule turned on, which is what causes the first error.
you cannot have both the base rule and our rule turned on, as the base rule will false positive.
see the docs on semi: https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/semi.md

the second one might be a bug, but it's hard to tell because you've clipped the code out.

I had the same problem as @bjerkins and just confirmed adding the following from @bradzacher's link fixed it. Thanks, Brad!

  "semi": "off",
  "@typescript-eslint/semi": ["error"]

why have you got both?

"semi: ["warn", "always"],
"@typescript-eslint/semi": ["warn", "always"],

This will ofc cause a problem because both rules are going to try and add a semi.

Please read the rule doc, which tells you to explicitly NOT do this.
https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/semi.md

why have you got both?

"semi: ["warn", "always"],
"@typescript-eslint/semi": ["warn", "always"],

This will ofc cause a problem because both rules are going to try and add a semi.

Please read the rule doc, which tells you to explicitly NOT do this.
https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/semi.md

sorry for deleting my last comment... just figured out what I'm messing with and didn't see someone already seen and replied lol ...