Deno: Remove buildin typescript compiler

[KnisterPeter]

Hi Ryan,

as discussed with you after your talk on JSConf, I would propose to remove the building typescript compiler. It could be easily supported by precompile your application and run the result in deno.
The build-in version of typescript will otherwise always be a bit outdated or you tie the deno release cycle to typescripts release cycles.

Otherwise: Keep going, this rocks :+1:

[kitsonk]

Personal opinion, but I disagree. The same logic could be used for v8, and that demo should be decoupled from the JavaScript engine.

While there is risk of breaking changes in any dependency, it is something that can be managed.

The assumption that you can have the whole programme to transpile would mean that remote TypeScript modules would not be possible. Bring able to support remote TypeScript modules that are still treated in a type safe way is a huge advantage of demo IMO.

[KnisterPeter]

Importing untranspiled typescript scripts would be removed then, you are right.
But I (personally) don't see that many value in it. But that may be only my opinion.

[ry]

Hi @KnisterPeter - I have been thinking about it since you brought it up at jsconf. Certainly not using TS is more minimal and I think that's usually the best strategy. However I disagree that TS getting out of date is going to be such a problem - TS is relatively stable at this point and if Deno ever becomes a thing I would imagine TS would be even more stable by then. I will keep pushing forward with TS in this next version of deno that I'm working on. However if it slows down startup time too much or there are other major issues - I will revisit this. The URL imports could be done via V8's import API, for example, instead of via TS's (A PR in v8worker2 adds hooks to these APIs https://github.com/ry/v8worker2/pull/3 )
I will close this for now.

[kitsonk]

@ry, as a side note, I have noticed a few things in the interfacing with TypeScript the could be more efficient. I realise that it must be like herding cats at the moment with all the input, so I won't distract you further at the moment, but if/when you want help with the next version of Demo, I would be glad to try to help make the TS interface as efficient as possible.