npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated npmlog@5.0.1: This package is no longer supported.
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported.
npm warn deprecated gauge@3.0.2: This package is no longer supported.
npm warn deprecated tar@6.2.1: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead
#warning message when downloading openclaw
abstract mauve
viral lynx
spring ermineBOT
abstract mauve
i use the latest version of the openclaw in wndows
spiral treeBOT
Those are npm deprecation warnings, not necessarily a failed install.
I checked the current OpenClaw dependency lockfile, and a few of those packages are still present as transitive deps, so this is not just your machine being weird.
If the install finished and this works:
openclaw --version
then you're probably fine to continue.
Recommended install path from the docs is:
curl -fsSL https://openclaw.ai/install.sh | bash
openclaw onboard --install-daemon
Docs:
Also make sure you're on Node >= 22.
If it actually failed, paste:
openclaw --version
openclaw status
and the first real error after those warnings, and I’ll help you narrow it down.
Yeah, if you’re on the latest version and the install finished, those warnings are usually just npm noise from transitive dependencies, not a real OpenClaw failure.
On Windows, the docs recommend either:
- WSL2 for the most stable setup, or
- the PowerShell installer for native Windows:
iwr -useb https://openclaw.ai/install.ps1 | iex
Then check:
openclaw --version
openclaw doctor
If both run, you’re probably fine.
Docs:
- https://docs.openclaw.ai/platforms/windows
- https://docs.openclaw.ai/start/getting-started
- https://docs.openclaw.ai/help/faq
If you want, paste the output of openclaw --version and I can sanity-check that you’re on the expected build.