The new implementation makes plugins a challenge, since there's no way we can load anything like that besides IPC or embedding a VM. Wwe don't get a runtime for free by being in JS. We have ported everything to parse, check, emit JSX in the new codebase (though not yet the actual JSX transforms). - ThreadSky

About ThreadSky

jakebailey.dev • 8 days ago

The new implementation makes plugins a challenge, since there's no way we can load anything like that besides IPC or embedding a VM. Wwe don't get a runtime for free by being in JS.

We have ported everything to parse, check, emit JSX in the new codebase (though not yet the actual JSX transforms).

Comments

runspired.com•8 days ago

So… then is it just dead in the water on arrival? Because svelte/vue/astro/mdx/ember etc only work because node APIs are able to be intercepted.

runspired.com•8 days ago

And fwiw, these plugins are literally just standard tsserver plugins, they only have to wrap ts to intercept file io just because tsc won’t accept the file extension on an otherwise parseable file otherwise. Everything else is via the plugin.

jakebailey.dev•8 days ago

Obviously that isn't the goal, it's just that the way things work will need to change. We're not in Node, there's no interception to be had per se, except what we explicitly provide (e.g., we're doing LSP, so it's likely that layer is where a plugin can happen)

remcohaszing.nl•6 days ago

I think this would be handled better by an IPC API, not LSP. LSP is for editor integration. Currently this is also true for plugins, but not having first-party support for plugins in the CLI, is a huge drawback.

remcohaszing.nl•6 days ago

I imagine something like a `tsc-node` bin which can handle plugins, at the cost of being slower. It would even be an improvement if it doesn’t support emitting. This would still be really useful for Astro/Svelte/Vue/MDX/CSS module/etc users, and even for frameworks that offer plugins, like Next.js.

dummdidumm.bsky.social•8 days ago

I thought that's what https://github.com/microsoft/typescript-go/discussions/455 is for - but so far it seems to be less of a priority which is kinda concerning. A "restart" with Go would be a great opportunity to provide good hooks into the TS core which would make hacking into internals unnecessary

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply