Hi @NotWoods, after a bit more thought I asked some question about this approach here #779 (comment)

I think I'm missing context on why is it necessary to commit the types/index.d.ts when the source is already typescript. I was expecting that file to be generated along side the js files before publishing to npm only. @shellscape Do you have more information on this?

I don't think the test:ts task is checking well the types. I checked this reverting locally the changes in #647 and it doesn't catch the error.
It did catch it if I directly run tsc --noEmit, because that runs on all ts files of the plugin.

So I know that historically we've had the the index.d.ts files hand-written before plugins were moved to TypeScript. That made an additional test of the types necessary. Some of those have stuck around. We even have some TypeScript-sourced plugins (maybe they're all like this still?) that have a separate, hand-written index.d.ts, which again is important to check against the code.

In the case of plugins which are already switched over to TypeScript sources, we should probably be generating the definitions at build time, and then removing the additional type check tests (as you point out, it'd be unnecessary). If we do that, for any plugin which uses generated definitions rather than the hand-written definition, we'll have to do a separate PR for each plugin.

Ok, sounds good @shellscape. But for the scope of this PR I managed to deliver the type checking by checking all the ts files in each package, not just the index.d.ts like before.

@NotWoods I've merged your proposed change.