Ryan Cavanaugh

> Our internal platform will resolve whatever you point it at. Just like the web. So it would be fine to deploy .ts files and have them import each other...

@robpalme and I discussed the emit vs `.ts` imports thing offline. TL;DR -- the scenario he describes above would still be well-supported. The nuance here is that we would still...

> Deno would be a case of a runtime that sees a .ts specifier, in a .js file, and really does mean to refer to a .ts file on disk...

This would seem to follow from the PR text https://github.com/microsoft/TypeScript/pull/40336 > Type inference supports inferring from a string literal type to a template literal type. For inference to succeed the...

> it is simply counter intuitive, because with never, we always expecting negative case What? `never` is defined to be the subtype of all types. ```ts type M = never...

Thinking about it more, I think the correct behavior is actually fairly straightforward when comparing this to object types (demonstrated below). Probably what's going wrong here is that we have...

> I've been deep-diving the issues related to this error and symlinks and pnpm specifically. Since 2019 it appears that this regression is reintroduced at least twice for each major...

Sorry, you're right. I've misconfused this with yarn.

@shellscape while I've got you here, we've been trying to reach `security@` pnpm.io regarding an issue we identified a while back, but haven't received a reply. Can you poke the...

> At least, an assignment of a function which doesn't have assertion function signature to an assertion-function-typed variable should be rejected. Original notes at #32695 don't mention this, but IIRC...