-
-
Notifications
You must be signed in to change notification settings - Fork 192
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
Cannot start language server #34
Comments
I assume you're referring this
This never gets release to npm. You would have to build from source to have this feature |
What are you trying to achieve? |
I’m trying to use it with the vim plugin ale. It supports language server checkers/linters. Sent with GitHawk |
The startServerProcess () {
return super.spawnChildNode([require.resolve('svelte-language-server/bin/server.js')], {
stdio: [null, null, null, 'ipc']
})
} Maybe you have more luck with that. But apart from that, we cannot help you right now. |
Another (neo)vim user here excited about the recent developments! A stable CLI released to npm would be awesome. I recently migrated my setup to CoC and there’s a svelte extension for it. There’s also an open issue which I assume will require something like this. |
Alright, I opened a new issue for the npm package topic. To answer the original question: This is not doable for this repo right now, only for the old. For the old one: From what I saw in the other IDE plugins so far, the path/command to starting the server is |
About the stdio support I mention before, you could refer to the original PR jamesbirtles/svelte-language-server#38 from origin repo. It's merged after the last release. |
We'll see how the deploy works tonight, but this might then be fixed |
Could you try some of the suggested solutions and tell us if it works? |
A CLI seems pretty easy to create if anyone wants to give it a shot: #68 |
The language-server is now regularly shipped 👍 and there's a svelte-check CLI |
I installed the
svelte-language-server
package and tried running it both without arguments:and with
--stdio
In both cases nothing happens. The command just exits immediately without any output. Exit code is also 0.
The text was updated successfully, but these errors were encountered: