neovim/node-host

Errors thrown in plugins hard to debug

dlants opened this issue · 5 comments

dlants commented

uncaught errors in plugins seem to be getting sent to stdout, which makes nvim close the channel (see neovim/neovim#4468 (comment) )

These errors are quite hard to find, and result in further plugin requests to show an unhelpful Invalid channel "3" message.

I think it's due to this

node-host/lib/plugin.js

Line 137 in 6ad15da

sandbox.process.stderr = self.stdout

I'm not sure if there's something better to do with stderr, but it would be great to send uncaught exceptions somewhere where they can be more obvious.

billyvg commented

Yep! Can I ask what plugin you are using, or are you writing a plugin? We are currently rewriting node-host and node-client. The new client will provide much better logging/debugging options.

dlants commented

I'm writing my own.

Any idea about when the new client will land? Will the API be similar?

billyvg commented

@dlants API will be very similar, biggest difference is it will be a Promise-only API.

justinmk commented

Please re-open at https://github.com/neovim/node-client if necessary.

https://github.com/neovim/node-host repro is deprecated.

Delapouite commented

@justinmk you may want to use this new GitHub feature to indicate clearly that repo is deprecated : https://github.com/blog/2460-archiving-repositories