Augment server cannot detect node version when using snaps

[aieri]

I am unable to use the nvim plugin on the current Ubuntu LTS (24.04).

If I install node.js from deb, the plugin complains that the version is too old (18.19.1 at the moment).
If I install the official node.js snap (22.16.0 at the moment), the Augment server is unable to detect the version and exits:

    3 2025-06-18 11:37:35 [INFO] Starting Augment Server v0.25.1                                                                                                                                                                                              
    2 2025-06-18 11:37:35 [INFO] Using workspace folders: [{'uri': 'file:///this/is/redacted/', 'name': 'git'}]                                                                                                                                           
    1 2025-06-18 11:37:35 [WARN] Failed to determine the Augment runtime version. Command `node --version` returned no output.                                                                                                                                
    4 2025-06-18 11:37:35 [ERROR] Augment exited: code: 0, signal 0         

While integrating with snaps can be a pain, both nvim and node are classic snaps so you shouldn't have to deal with plugs and connections.

$ snap list nvim node
Name  Version  Rev    Tracking       Publisher    Notes
node  22.16.0  10226  22/stable      iojs✓        classic
nvim  v0.11.2  3834   latest/stable  neovim-snap  classic

I'm not sure why Augment says node --version returns no output... from which context is this command being run?
FTR, my user can run this without problem, as expected:

$ node --version
v22.16.0

[NobbZ]

Are you starting neovim from a terminal? When you do so is the node in PATH? If you aren't, does starting from a terminal change the behaviour?

Does setting vim.g.augment_node_command to an absolute path of the node binary change anything in either situation?

[aieri]

Yes, I run nvim from terminal and node is in the PATH:

$ which node         
/snap/bin/node

$ echo $PATH | grep -o snap/bin      
snap/bin

Additionally:

$ snap run --shell nvim 
andrea.ieri@A02511:~$ node --version
v22.16.0

...which tells me node should be reachable and executable just fine within the nvim snap context.

Setting vim.g.augment_node_command = "/snap/bin/node" yields the following failure:

    3 2025-06-20 11:28:26 [WARN] Failed to determine the Augment runtime version. Command `/snap/bin/node --version` returned no output.                                                                                                                      

And yet...

$ snap run --shell nvim 
andrea.ieri@A02511:~/work$ /snap/bin/node --version
v22.16.0

That said, I have now noticed that the Lazyvim plugin also fails to execute node if node is a snap, as well as go (which is also a snap on my system) so the bug is likely to be elsewhere

[aieri]

Ok, I've tried installing neovim from the PPA and I am now able to use the Augment plugin. In summary, as long as only node xor neovim are snaps, things work properly. I'll close this bug report and try discussing this issue with the snapcraft team.