Ryan Cavanaugh

NodeJS shipping `--experimental-strip-types` means there's now an actual runtime scenario where you need *both* JS and TS extensions

Note that if you're using this *in any other situation than that*, you likely have a misconfiguration or misunderstanding of some kind, and I'll be telling you as much in...

Imports in `.d.ts` files are allowed to use `.ts` extensions regardless of config, so I wouldn't really consider that a bug.

> Also, it currently (?) does not support aliases which resolve to a relative path. This is 100% intentional

I don't think the setup you have there works under `--experimental-strip-types`. https://github.com/microsoft/TypeScript/pull/59767#issuecomment-2383844756

I can't replicate what you're doing there ```ts // with // import * as bar from "./bar.ts"; node --experimental-strip-types foo.ts hi ``` vs ```ts // with // import * as...

Let's revisit this when the need arises. For now, we'd like to keep the TS6/TS7 delta as small as possible.

The results at #59683 outline the difficulty of this. Looking at the code, we see a lot of places where people write code that takes an implicit dependency on the...

We don't need comments to be aligned between the two codebases, no

Yes, this is functioning correctly. The types are equivalent and we have never instructed anyone to take a dependency on the text representation of a union type, nor would we.