atom-languageclient fails on hacked up JSON it tried to send itself(?) about atom-languageclient

[damieng]

By default language servers use stdout and stdin to communicate. If your server is using console.log to write out what it gets that will be be sent back to atom-languageclient and could easily cause this error.

If you're using the vscode-languageserver library to manage the connection you can wire up console.log and console.error to instead send back log and error messages over json-rpc which will show in the console.log in Atom by adding two lines after your createConnection, e.g.

const connection = createConnection()
console.log = connection.console.log.bind(connection.console)
console.error = connection.console.error.bind(connection.console)

I wrote something from scratch which doesn't output anything - at least it's not supposed to, and in all manual tests it never did.

Interestingly, my log shows I got proper complete JSON-RPC requests from Atom though, so I'm not sure what exactly the atom-languageclient error popup is so confused about..

[damieng]

How are you writing your log out?

This is probably also related to me using stdin/stdout wrong as in #24 - since I switched to TCP ports that strange behavior is gone. Since my stdin/stdout use was quite hackish anyway, I'll assume here as well that this was in the end a bug on my side, and since I use TCP now all works fine.