EINVAL

[xuezhenqiang000]

codegraph -v
codegraph: spawnSync D:\Application\dev-app\nvm\v24.11.0\node_modules@colbymchenry\codegraph\node_modules@colbymchenry\codegraph-win32-x64\bin\codegraph.cmd EINVAL

[xuezhenqiang000]

codegraph init -i
codegraph: spawnSync D:\Application\dev-app\nvm\v24.11.0\node_modules@colbymchenry\codegraph\node_modules@colbymchenry\codegraph-win32-x64\bin\codegraph.cmd EINVAL

[xuezhenqiang000]

There were issues installing via npx or npm, but fortunately, downloading the release directly works fine. Perhaps there's an issue with my environment.

[ayu-exorcist]

Hi @xuezhenqiang000,

This should be fixed by #291.

Root cause: The npm thin-installer shim (scripts/npm-shim.js) uses child_process.spawnSync() to launch the bundled codegraph.cmd on Windows. Node.js requires shell: true when spawning .cmd batch files -- without it spawnSync throws EINVAL on newer Windows/Node combinations.

Fix: A one-line change adding shell: process.platform === 'win32' to the spawnSync options.

You can try the fix once it lands in a release, or test it locally by editing node_modules/@colbymchenry/codegraph/scripts/npm-shim.js inside your global npm install and adding shell: true to the spawnSync call.

[colbymchenry]

This landed in #292 (merged to main) and will ship in 0.9.2. Thanks @ayu-exorcist for #291 and the diagnosis as well — both pin the same root cause.

Root cause: the npm installer is a thin shim that locates the per-platform bundle and spawns its launcher. On Windows that launcher is a .cmd batch file, and the shim spawned it directly. Modern Node on Windows refuses to spawn .cmd/.bat without shell: true (the CVE-2024-27980 hardening), so on Node v24.11.0 it threw spawnSync …\codegraph.cmd EINVAL. Not your environment — a real bug for every Windows npm/npx install on recent Node.

Fix: on Windows the shim now invokes the bundled node.exe against the app entry directly, bypassing the .cmd (rather than shell: true, which doesn't auto-quote args on Windows). Verified end-to-end against a real win32-x64 bundle — npm install of the packed tarballs + codegraph init -i/status running on the bundled Node 24, no more EINVAL.

Until 0.9.2 is published to npm, the GitHub Release download you switched to is the right workaround. Once it's out, npm i -g @colbymchenry/codegraph and npx will work on Windows again. 🙏

[colbymchenry]

@xuezhenqiang000 I've released v0.9.2.

[xuezhenqiang000]

Thank you @ayu-exorcist for the quick diagnosis and @colbymchenry for the fast fix and v0.9.2 release! The issue is resolved now. Really appreciate it! 🙏