Excited to see how well Deno's security features pan out under broader, real-world usage.
if VS Code already supports TypeScript, what is missing?
My understanding is prior to this release the Deno LSP didn’t have visibility into types from packages originating from NPM.
Compatibility issues likely still exist, but I suspect the scope of work for an MVP substitution of Node for Deno is in the realm of possibility now when it wasn’t before.
``` import { Example } from "./example.js" // the actual file is example.ts ```
While in Deno you actually import the typescript file ``` import { Example } from "./example.ts" ```
That difference alone was enough to trip up the built-in typescript language tool and add friction.
Another thing is that Deno has a built in formatter / linter, you don't use a 3rd party tool like eslint, so having the ide just know how to do the linting and formatting is nice, the default typescript language plugin can't do that.
Also, Deno formats other file types including json, yaml and markdown.