> Which you import just like you would in a browser.
Import them from where?
Also, if I have more than 10 packages, it makes sense to bundle them
> While not exactly a second class citizen, losing Typescript (if it comes to that) is something the platform can survive.
That is not what I asked/pointed out
> Import them from where?
A url. The files are cached. You can always explicitly vendor dependencies and use relative imports (or import maps) if you don't want to rely on random urls.
> Also, if I have more than 10 packages, it makes sense to bundle them
And Deno has a built-in bundler.
Which you import just like you would in a browser.
> Does Deno implement its own TypeScript compiler?
Deno is a JS engine that aims for maximum compatibility with browsers.
While not exactly a second class citizen, losing Typescript (if it comes to that) is something the platform can survive. Ryan is on record saying that adding Typescript support at a very early stage was probably a mistake.[1]
[1] https://www.youtube.com/watch?v=vBd4tPUBUQo