-
Notifications
You must be signed in to change notification settings - Fork 689
Open
Description
Environment
- OS: Windows
- Node.js: compatible with the package requirement (>=18)
- npm: global install
What I ran
npm uninstall -g @googleworkspace/cli
npm cache clean --force
npm install -g @googleworkspace/cli
gws auth setup
What happened
The command fails with:
Error: spawnSync C:\Users\Hanekawa\AppData\Roaming\npm\node_modules\@googleworkspace\cli\node_modules\.bin_real\gws.exe ENOENT
at Object.spawnSync (node:internal/child_process:1119:20)
at spawnSync (node:child_process:911:24)
at C:\Users\Hanekawa\AppData\Roaming\npm\node_modules\@googleworkspace\cli\binary-install.js:197:24
at process.processTicksAndRejections (node:internal/process/task_queues:104:5) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawnSync C:\\Users\\Hanekawa\\AppData\\Roaming\\npm\\node_modules\\@googleworkspace\\cli\\node_modules\\.bin_real\\gws.exe',
path: 'C:\\Users\\Hanekawa\\AppData\\Roaming\\npm\\node_modules\\@googleworkspace\\cli\\node_modules\\.bin_real\\gws.exe',
spawnargs: [ 'auth', 'setup' ]
}
Verification
I checked whether the expected binary exists:
Test-Path "C:\Users\Hanekawa\AppData\Roaming\npm\node_modules\@googleworkspace\cli\node_modules\.bin_real\gws.exe"
Result:
False
So the package appears to install successfully via npm, but the actual Windows binary is missing from the location the wrapper expects.
Expected behavior
npm install -g @googleworkspace/cli should install or place gws.exe in the expected path so gws auth setup can run.
Notes
This looks like a packaging/install-script issue specific to Windows, rather than a Node version issue.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels