IMPORTANT: Archiving typescript.nvim

[jose-elias-alvarez]

I am no longer using Neovim as my primary editor, so I am archiving the typescript.nvim repository on on August 11, 2023 (about one month from today). Any user or organization who wants to fork the project and take over maintenance should feel free to do so (I do not plan on transferring the repo).

I will be traveling for most of July and do not plan on reviewing issues or merging PRs between now and the archival date. If there’s interest in and community consensus on a fork, I will update the README to direct users there and mention it in the final archival notice commit to make users aware via their plugin managers, but otherwise, typescript.nvim will remain as-is.

Barring breaking changes to typescript-language-server, the plugin will likely continue working for the foreseeable future, so if you’re happy with its current functionality, feel free to create a personal fork or straight-up copy-paste the generated code. You can also try typescript-tools.nvim, which is under active development (I don’t agree with its fundamental approach, but practically speaking it should work just as well as or better than typescript-language-server).

[jacksonludwig]

Thanks for your contributions! And good luck on your traveling.

Curious also, what editor are you using instead now?

[magoz]

Thank you for your work over the years!

[mawkler]

You can also try typescript-tools.nvim, which is under active development (I don’t agree with its fundamental approach [...]

Could you elaborate on what you disagree with please? I'm very curious.

Also, thank you very much for your hard work!

[jose-elias-alvarez]

Thanks to everyone for their kind words of support. I hate to disappoint, but I'm not interested in commenting on editor choices.

You can also try typescript-tools.nvim, which is under active development (I don’t agree with its fundamental approach [...]

Could you elaborate on what you disagree with please? I'm very curious.

The current state of TypeScript editor tooling is an absolute mess (entirely of Microsoft's making), and I understand the desire to achieve feature parity in your preferred editor (it's what motivated me to make nvim-lsp-ts-utils), but the whole point of the Language Server Protocol is to avoid reinventing the wheel. I think the only way to escape this cycle is to put effort into LSP tooling, not creating more bespoke solutions.

That's really an ideological concern, though, and practically speaking the approach typescript-tools is taking should lead to something closer to tsserver parity. I haven't tried it myself, but it seems like a good solution for devs who just want things to work.

[yioneko]

The current state of TypeScript editor tooling is an absolute mess (entirely of Microsoft's making)

For anyone interested in this, see microsoft/TypeScript#39459. Unfortunately, till now ts team doesn't seem to have any schedule to officially adopt LSP to their server.

One promising solution for this is volar.js, which is originally designed for vue language server but now expanded as a general language server framework. It contains a TypeScript language service (not tsserver) to be able to directly used as a library and easily adapted to LSP. In the future, the author of volar, which works full-time on this, could improve the whole ecosystem of TypeScript tools.

And at last, great appreciation to your work, which partially lead me to make vtsls.