Could not determine Node.js version

[neonvoidx]

After updating today over the weekend, getting this error, this has always worked for me

[Copilot.lua] Could not determine Node.js version
-----------
(exit code) -1
   (output) [no output]
-----------

Current config:

  {
    "zbirenbaum/copilot.lua",
    event = "InsertEnter",
    opts = {
      filetypes = { markdown = false, help = false },
      copilot_node_command = vim.fn.expand("$FNM_DIR") .. "/node-versions/v22.13.0/installation/bin/node",
    },
  },

Output of vim.fn.expand("$FNM_DIR") .. "/node-versions/v22.13.0/installation/bin/node":
/Users/jrreed/Library/Application Support/fnm/node-versions/v22.13.0/installation/bin/node

 ls '/Users/jrreed/Library/Application Support/fnm/node-versions/v22.13.0/installation/bin/'
 corepack   mmdc   node   npm   npx

[neonvoidx]

Looks like it started here f122741

I have the same issue

[Crowly34]

I find it curious that I'm having the same issue, but "node" works, and we both pass Application Support, maybe its an escaping issue? the codebase parser stopped working like it used to?

[AntoineGS]

@timhugh are you able to take a look? I won't be able to for a few more days unfortunately. 😕

[Crowly34]

@AntoineGS might have been this split, its considering anything after a space an arg I think, let me see if I can come up with something and push a PR or at least suggest

CC @timhugh actually, seems to be a PR you introduced so maybe you have a better insight here.

https://github.com/zbirenbaum/copilot.lua/pull/527/files#diff-9a3cfd5f86db1182e4f6c1c357b97be0c0bf6f2a9d5a050bc8db812f556ee759R99

[AntoineGS]

Awesome thanks!

[Crowly34]

@AntoineGS @timhugh I want to check expectations here I think I found the issue and a simpler path forward:

The problem is how we’re handling copilot_node_command. In #527 we tried to solve it with vim.split(), but that introduces bugs when the node path contains spaces. Instead, I think we can safely rollback that change and just rely on vim.system(), which already supports both string and string[].

That way:

• If users just want a path/executable, they set a string ("node" or "/path with spaces/node").
• If they need extra args, they pass an array (e.g. {"mise", "x", "node@24", "--node"}).

The PR needs to be just an update to validation and docs.

[timhugh]

• If users just want a path/executable, they set a string ("node" or "/path with spaces/node").
• If they need extra args, they pass an array (e.g. {"mise", "x", "node@24", "--node"}).

This is a great idea! The fix here undid my fix (totally understandably), so I ran with your idea here and added much-needed test coverage so we don't regress on either of these use cases: #552

[Karl-EdwardJeanMehu]

Any idea on how to fix this?

[Crowly34]

@Karl-EdwardFPJeanMehu update copilot nvim package, and this specific issue should be solved.

[ubbabeck]

I still am having this issue,

When I run Copilot verion

[Copilot.lua] Neovim 0.11.5
copilot language server 1.396.0
copilot.lua e919876a5523b06406f0bc7285477da87a338a61
Node.js 
Language server: nil

Update, it was a path issue, you may disregard this comment.