Skip to content

Conversation

@blackxored
Copy link

Adds vtsls as a language server for TypeScript, with Vue support.

Vue support these days seems to require both vtsls as a language server and the vue_ls server, the setup is not a one-liner, that's why I thought to add it as a single switch with this module.

lspconfig.<server>.setup is not working for me here, despite updating nvim-lspconfig (part of this PR regardless), perhaps related to how or when nvf enables servers, or due to one (vue_ls) depending on another.
Side effect, it seems that these configs are always on with this method (check :LspInfo on blank) whereas other LSPs are not, it doesn't bother me much since they don't activate on everything.

Sanity Checking

  • I have updated the changelog as per my changes
  • I have tested, and self-reviewed my code
  • My changes fit guidelines found in hacking nvf
  • Style and consistency
    • I ran Alejandra to format my code (nix fmt)
    • My code conforms to the editorconfig configuration of the project
    • My changes are consistent with the rest of the codebase
  • If new changes are particularly complex:
    • My code includes comments in particularly complex areas
    • I have added a section in the manual
    • (For breaking changes) I have included a migration guide
  • Package(s) built:
    • .#nix (default package)
    • .#maximal
    • .#docs-html (manual, must build)
    • .#docs-linkcheck (optional, please build if adding links)
  • Tested on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin

Add a 👍 reaction to pull requests you find important.

@github-actions
Copy link

github-actions bot commented Jul 30, 2025

🚀 Live preview deployed from e35a74c

View it here:

Debug Information

Triggered by: blackxored

HEAD at: lsp/vtsls

Reruns: 1168

@horriblename
Copy link
Collaborator

hi, we're moving away from lspconfig in v0.8 #1018, as such, we are freezing changes to the language module until the work there is done. If you want to, you can use the new approach in v0.8 and make a PR for after we get that merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants