Chris Krycho

The solution here appears to be just as simple as making sure that when doing `--declaration`, the *emitted file* has the full specifier name, right? `.gts.d.ts` should do the trick...

> if someone imports a file with the extension in one place, but then without the extension in another place, then you can't have the import resolve correctly in both...

It would definitely be convenient, but/and `yargs` does *not* supply a good interface for it.

While I see the issue you all are trying to solve here, I would humbly suggest that the right answer is probably… add a signature instead? There are *sharply* diminishing...

:+1: We'd very much welcome a code fix!

Thanks for opening this! The fact that CI is ✅ is a great initial sign – one of us will try to review in detail shortly.

We've thrown around the idea (in both Framework and TS contexts) of making something like this work: ```ts interface GreetingSig: { Args: { message: string } } const Greeting =...

One reason that we haven't pushed forward on that is: you can provide a *default* type parameter for what a `Controller` is, but there's no way to *constrain* it to...

Oh, that's interesting. …I still don't want it. 😂

Thanks for the report; this seems like a case where Glint should be bailing and is not! Do you happen to have a minimal reproduction of this? --- Aside: In...