[Bug]: Windows: Command parsing treats executable path as first argument, causing all commands to fail

[JaeGerW2016]

Description

After installing opencli on Windows, executing any command results in an error:

error: unknown command 'C:\Program Files\LobsterAI\node_modules@jackwener\opencli\dist\main.js'

Root Cause

On Windows, opencli incorrectly parses command-line arguments and treats its own script path (the full path to main.js) as the first command argument instead of recognizing it as the executable file itself.

Steps to Reproduce

1. Install: npm install -g @jackwener/opencli
2. Run: opencli list
3. Error: error: unknown command 'C:\Program Files\LobsterAI\node_modules@jackwener\opencli\dist\main.js'

Expected Behavior

1. Direct execution: opencli list → Failed
2. Full path: node "C:\Program Files\LobsterAI\node_modules@jackwener\opencli\dist\main.js" list → Failed
3. Wrapper script: Created opencli-wrapper.cmd → Failed
4. Source installation: Cloned from GitHub and installed → Failed

OpenCLI Version

1.4.1

Node.js Version

22.x

Operating System

Windows

Logs / Screenshots

[Astro-Han]

This is likely caused by spaces in the install path C:\Program Files\. The .cmd wrapper generated by npm on Windows may incorrectly split process.argv when the path contains spaces, causing Commander.js to treat the script path as a command argument.

Workaround:

• Change the global npm prefix to a path without spaces (e.g. C:\tools\nodejs\) and reinstall globally
• Or when using node directly, make sure the path is quoted: node "C:\...\main.js" list

If it still reproduces with a space-free path, please share the output of node -e "console.log(JSON.stringify(process.argv))" alongside the full error output from opencli, so we can pinpoint the exact argv parsing issue.

[JaeGerW2016]

邮件已收到