-
-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Suggestion]: separate vetur server to a standalone package #168
Comments
Hi @octref . I have extracted vetur server into a separate repo. https://github.com/HerringtonDarkholme/vue-language-server Is this fine? |
That's fine, but I'm wondering how you are gonna update it as I update the code for the server. Now after a while I think I should just close the repo https://github.com/octref/vls and merge it back to vetur, so I can deal with all issues at the same place. |
I deprecated vls and put the code under |
I finally decided to fork out vetur server. Some progress here:
|
I don't think that's a good idea, because then I wouldn't know the where the bugs come from. But good job on the Stylus IntelliSense! Are you thinking about merging or just keep maintaining your fork? |
Vetur is a great vscode plugin. And its implementation has already in par with language server protocol.
It would be even greater if server code can be separated into a standalone package so other editor users can share this great language service via language service client.
The text was updated successfully, but these errors were encountered: