Summary

The Windows installer (install.ps1) fails because it attempts to execute npm using node.exe on a JS entry file. On Windows, npm is exposed as a .cmd shim, so the installer cannot find the expected file, resulting in npm error code ENOENT.

Suggested fix: Replace node-based invocation with a direct global npm installation:

npm install -g moltbot

Steps to reproduce

Install Node.js (tested on Node 24 LTS) on Windows 10 Pro 22H2.

Open PowerShell and run the installer:

iwr -useb https://molt.bot/install.ps1 | iex

Observe the installer fails with npm error code ENOENT.

Expected behavior

The installer should correctly install Moltbot and make the moltbot command available in PowerShell.

Actual behavior

Installer outputs:

node.exe : npm error code ENOENT

The moltbot command is not recognized in PowerShell.

Manual global installation works:

npm install -g moltbot

Environment

Moltbot version: 2026.1.24

OS: Windows 10 Pro 22H2

Install method: PowerShell script (install.ps1)

Node.js version: 24.13.0 LTS

npm version: 10.9.4

Logs or screenshots
PS C:\Users\User> iwr -useb https://molt.bot/install.ps1 | iex

Moltbot Installer

[OK] Windows detected
[OK] Node.js v24.13.0 found
[*] Installing Moltbot@latest...
node.exe : npm error code ENOENT
位於 線路:1 字元:1

• & "C:\Program Files\nodejs/node.exe" "C:\Users\User\AppData\Roaming\n ...

•   + CategoryInfo          : NotSpecified: (npm error code ENOENT:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError