However, before neovim 5.1.0 (node-client npm package), the native logs (console.log) were actually inside vscode natively but there was a bug that were not redirecting them into the custom logging system. see https://github.com/neovim/node-client/issues/329#issuecomment-2009676355 so it may actually be possible to use vscode debug console alternatively to writing them to a file.
It might be worth investing this again to see if we can get it to work with recent node-client.
With https://github.com/cursorless-dev/cursorless/issues/2331 we support visualising logs inside vscode by spawning a task that does
tail -f logfile
.However, before neovim 5.1.0 (node-client npm package), the native logs (
console.log
) were actually inside vscode natively but there was a bug that were not redirecting them into the custom logging system. see https://github.com/neovim/node-client/issues/329#issuecomment-2009676355 so it may actually be possible to use vscode debug console alternatively to writing them to a file.It might be worth investing this again to see if we can get it to work with recent node-client.