search

microsoft / vscode-languageserver-node

Language server protocol implementation for VSCode. This allows implementing language services in JS/TS running on node.js
MIT License
1.48k stars 325 forks source link

Error: spawn EINVAL when starting the Language Server #1545

Closed tiltue closed 3 months ago

tiltue commented 3 months ago

I get the following error when I start my extension: image

I already tried many different versions of all components, but nothing seems to work. I am currently working with: "@types/node": "^14.14.14",
"vscode-languageclient": "^7.0.0", "vscode": "^1.1.37", "@types/vscode": "^1.89.0" This configuration used to work a few weeks ago, but suddenly with no noticeable changes I got this error.... Does anyone experience the same issue? Any help is highly appreciated.

dbaeumer commented 3 months ago

In which language is the server written. Usually an error like this points to an invalid path.

tiltue commented 3 months ago

Thank you very much for your answer. The server is written in Scala. What kind of invalid path?

tiltue commented 3 months ago

I also opened another issue here, since I got a different error message after trying some different versions of the npm packages.

raycar5 commented 3 months ago

likely related to https://github.com/nodejs/node/issues/52554 I'm running into the same issue with the kotlin language server, a different cursor installation with an older version of node (20.9) works but vscode with node version 20.14 does not

raycar5 commented 3 months ago

I have just installed vscode 1.91 and the error is gone, nodejs version 20.9

tiltue commented 3 months ago

Thank you very much for your recommendation, I tried those versions but unfortunately, it is not working for me...

raycar5 commented 3 months ago

@tiltue try 1.91, I accidentally wrote 1.92 on my last message, which is the latest version and obviously not what I meant, sorry 😅

dbaeumer commented 3 months ago

@raycar5 thanks for the pointers. We (in VS Code) got actually hit by this as well ;-)

dbaeumer commented 3 months ago

I will close the issue since this is caused by NodeJS itself.