TypeScript Native / TypeScript 7 (`@typescript/native-preview`, `tsgo`) Support

[ShGKme]

What problem does this feature solve?

TypeScript on Go (also known as TypeScript 7 or TypeScript Native) has been released as a public preview.
Developers can try it via:

• npm package @typescript/native-preview with tsgo CLI
• VSCode Extension TypeScript (Native Preview)

It would be nice if it were possible to use it in the Vue ecosystem as well

What does the proposed solution look like?

• Support a switch in the config to use tsgo instead of tsc
• Do not patch TypeScript and instead add additional configuration to the TypeScript itself (supported extensions)

[john-landgrave]

So before the most recent update, setting hybrid mode to false actually allowed for a reasonable hybrid mode (ironically) where the TS Go server would provide intellisense and such for non-.vue files and the Vue extension (this one) would use the built-in TS server (or whatever you had selected via the old options) for .vue files. It wasn't perfect and wasn't necessarily what you are asking for here, but it was workable. Now it seems like we have to pick between one or the other and this extension doesn't seem to play nice with the TSGo preview.

Would love for either a way to turn hybrid mode back off (which seems unlikely because of some of the comments in the release notes) or this compatibility to work!

[JE-lee]

we need to make more progress

[aphex]

Hey all, bumping this.

I assume this ticket has to close to get support into the VSCode Extension. The tsgo performance is a huge improvement for our codebase already but sadly does not work in vue files. This also has an upstream tag, is there somewhere else this is blocked by? Another issue I can have eyes on? thanks!

[kalvenschraut]

We are basically stuck waiting until js plugin interop is available which is how volar currently runs with the tsserver currently which there are issues on the typescript go repo talking about this but doesn't seem to be an immediate concern for them.
microsoft/typescript-go#648
microsoft/typescript-go#455

Only option I know of would basically be a full go rewrite going the approach of how tsgolint is shimming the typescript-go code https://github.com/oxc-project/tsgolint

I am not one of the activate maintainers of this repo but above is how I understand it with my own research and experience

[segevfiner]

It's kinda early stages for the Go reimplementation of TypeScript, so plugins are probably not a priority just yet... Though they never have seen to be even in the original TypeScript and Volar still works by monkey patching rather than a clean and stable TypeScript plugin API... And such an approach can be significantly more difficult in a statically compiled language like Go, so I do hope they will add some stable API for the purpose of tools like Volar be it in Go or JS, or both.

[Tenrys]

For the time being, reverting to 2.2.10 and having hybrid mode off seems like a decent enough solution. At the very least, if TS is gonna be slow (at least on my specific project), it'll be mostly on the Vue SFCs.

[andreasgangso]

As AI agents are becoming faster, we'll need the tools around linting and typechecks to keep up with them. This is one of the bottlenecks for me to be using ai agents at max efficiency right now

[silverwind]

Maybe SFC parsing could be contributed into tsgo, e.g. without a plugin. Then there won't be a need for a vue-tsgo.

[acrobid]

New post on the issue by Microsoft

Of note:

Resetting Language Service Issues
While most of the core type-checking code has been ported over without any behavioral differences, the language service is a different story. Given the new architecture, much of the code that powers completions, hover tooltips, navigation, and more, has been heavily rewritten. Additionally, TypeScript 7.0 uses the standard LSP protocol instead of the custom TSServer protocol, so some behavior specific to the TypeScript VS Code Extension may have changed.

As a result, any bugs or suggestions specific to language service behavior are likely not to reproduce in the 7.0 line, or need a “reset” in the conversation.

These issues are very time-consuming to manually verify, so instead we’ll be closing existing issues related to language service behavior. If you run into an issue that was closed under the “7.0 LS Migration” label, please log a new issue after validating that it can be reproduced in the native nightly extension. For functionality that is not yet ported to 7.0, please wait until that functionality is present before raising a new issue.

[davidAtInleague]

Would it be possible to support this "just" on the command line for the time being, something like npx vue-tsc --experimental-use-tsgo?

[so1ve]

Would it be possible to support this "just" on the command line for the time being, something like npx vue-tsc --experimental-use-tsgo?

tsgo does not currently provide customization capabilities (plugins, monkey patching) like tsc. So the answer is no.