Closed martinkruusement closed 1 year ago
Looking at full server log, the server is actually starting correctly and that message doesn't show up until later. It appears that the message is triggered when the eslint LSP server tries to invoke eslint
in a subprocess which just suggests that eslint server doesn't support bun for some reason. So the issue is in https://github.com/microsoft/vscode-eslint or bun itself. I would guess the former.
For the moment, switching out node path to:
Throws an error due to Bun's welcome being message included in the initial payload:
Adding --silent here doesn't help either:
Not sure if this is Bun not receiving or honoring
--silent
or there actually isn't a way to turn it off and the message needs to be parsed out manually.Getting this to work would be awesome, will get rid of a lot of mjs / cjs eslint-config incompatibility pains.