Native TypeScript (v7) plans #3068
Replies: 1 comment
-
|
I believe we're 6-12 months away from even getting started on using the Go API. The API for the Go version is planned, but hasn't even been started yet: https://github.com/microsoft/typescript-go?tab=readme-ov-file#what-works-so-far I asked Jake Bailey about it earlier this month and he let me know the team has been very busy with editor functionality and alignments. TS 7.0 will almost certainly release without an API, but the API might be available in 7.1. As for how this will affect typedoc, it is truly too early to say. I suspect that it may break some functionality where typedoc depends on internal APIs which aren't going to be available in 7.x, but Jake also told me the team was going to make more things public on request, so while it might take some time, we should hopefully be able to keep most functionality alive. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
With apologies for a very open-ended issue, I was wondering what TypeScript's eventual migration to Go...
... means for TypeDoc? It seems like TypeDoc depends on the TypeScript JS/TS API extensively:
If it's not a concern, cool! If it's a worrying situation and upvotes on particular typescript-go issues would be helpful, that'd be great to know. Or if (more likely) it's too early to tell, maybe having an issue is helpful for anyone who wants to subscribe to updates on the question.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions