elevenlabs/cli bug (windows)

[LeConsulat2]

Hi ElevenLabs Team,

I’m encountering an issue with @elevenlabs/cli on a Windows (PowerShell) environment when attempting to add components.

Issue

The CLI consistently fails with the following error:

Error: npx is not available. Please install Node.js/npm.

Environment

• OS: Windows (PowerShell)
• Node.js: v20.19.6
• npm: v11.11.0
• Node managed via nvm for Windows

What I’ve Tried

I attempted multiple invocation methods:

npx @elevenlabs/cli@latest components add bar-visualizer

npm exec -- @elevenlabs/cli components add bar-visualizer

C:...\npx.cmd @elevenlabs/cli components add bar-visualizer

All of the above result in the same error.

Verification

• node, npm, and npx are all installed and working as expected
• npx is resolvable in the shell (Get-Command confirms this)
• The error occurs consistently regardless of how the CLI is invoked

Observation

Given that npx is available and functional in the environment, it appears the CLI may be performing an internal check that does not correctly resolve npx on Windows (potentially related to how .ps1/.cmd scripts are handled or how child processes are spawned).

Expected Behavior

The CLI should detect npx correctly and proceed with component scaffolding.

Please let me know if additional logs or details would be helpful.

Kind Regards,

[kraenhansen]

Thank you for reporting this. I can confirm the root cause: the npx availability check uses spawnSync without shell: true, which prevents Windows from resolving npx.cmd/npx.ps1. I'll put up a fix.