Regarding the typescript6 compatibility package, typescript native preview and the vs code extensions

[Simen Wiik (revosw)]

This is my understanding after reading the beta announcement blog post and browsing node_modules.

Typescript native preview (which I have been using since december) includes the tsgo.exe executable. There is a companion vs code extension, typescript native preview, that I think hardcodes to use tsgo.exe. The reason I assume that is because the native preview npm package does not have its own tsserver.exe, which I assume is specifically for the language server.

The typescript6 package includes tsc.exe (typescript 7), tsc6.exe (typescript 6) and tsserver.exe. My question is, can I uninstall both the @typescript/native-preview npm package and the typescript native preview vs code extension, and go back to using the regular typescript package?

In other words, is it correct to assume that this is the timeline?

Before native was introduced:

• npm i typescript
• Install the typescript vs code extension

When native was introduced:

• npm i @typescript/native-preview
• Install the native preview vs code extension

Now with the compatibility package

• Set typescript version to "typescript": "npm:@typescript/typescript6@^6.0.0" in package.json
• Uninstall @typescript/native-preview
• Uninstall native preview vs code extension
• The typescript extension now uses tsc.exe (typescript 7) under the hood