Insofar as we take `.ts` files seamlessly yes -- though to be clear, one does not simply "run" TypeScript. There are no runtimes for TypeScript directly (there's AssemblyScript that _looks_ like TypeScript, but isn't exactly TypeScript)

We've simply incorporated the type-checking and transpiling steps into the deno cli, making it super simple to get going, no config needed.

This is actually quite confusing, because

> A secure runtime for JavaScript and TypeScript.

Shouldn't require caveats, with the caveat being that there is no runtime for TS.

There is reason to believe that the extra information given from TS typings could be carried into runtime wins, and so there is absolutely pent up demand for an actual TS runtime.

Exactly. And I guess the package still needs to be compiled to JS before deploying to production? To avoid shipping a full TS compiler on a production server which would be a crazy thing to do.

I don't think that would be that crazy, especially if it's in the stdlib.

It seems like a huge amount of code and potential vulns to bring in production for no good reasons.

Why do you need a full TS compiler - you can just strip type annotations ala babel.