Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Regression][2026.4.21] npm global install still triggers bundled extension MODULE_NOT_FOUND [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#70526•Fetched 2026-04-24 05:56:57
View on GitHub
Comments
2
Participants
3
Timeline
3
Reactions
1
Author
liaoandiliaoandi
Participants
dysanfdysanfliaoandiliaoandisteipetesteipete
Timeline (top)
commented ×2closed ×1

On OpenClaw 2026.4.21, a fresh global npm install still causes cascading MODULE_NOT_FOUND errors from bundled extensions, and openclaw status / openclaw health become unreliable.

Root Cause

On OpenClaw 2026.4.21, a fresh global npm install still causes cascading MODULE_NOT_FOUND errors from bundled extensions, and openclaw status / openclaw health become unreliable.

Fix Action

Workaround

Install dependencies in extension directories, then restart gateway:

  • For each dist/extensions/*/package.json that declares dependencies, run: 
    npm install --prefix <extension_dir>
  • Restart gateway service(s)
  • Re-run openclaw status / openclaw health

Code Example

npm install -g openclaw@2026.4.21

---

openclaw status
   openclaw health

---

npm install --prefix <extension_dir>
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

On OpenClaw 2026.4.21, a fresh global npm install still causes cascading MODULE_NOT_FOUND errors from bundled extensions, and openclaw status / openclaw health become unreliable.

Environment

  • OpenClaw: 2026.4.21
  • Install method: npm install -g [email protected]
  • OS: macOS 26.4.1 (arm64)
  • Node: v25.9.0

Steps to reproduce

  1. Fresh install: 
    npm install -g [email protected]
  2. Run: 
    openclaw status
openclaw health
  3. Observe module resolution failures from bundled extensions.

Actual behavior

Observed errors include:

  • Cannot find module @larksuiteoapi/node-sdk
  • Cannot find module nostr-tools
  • Cannot find module @slack/web-api

In this state, status/health fail or become unstable.

Expected behavior

A fresh supported install should have all required bundled extension runtime dependencies, and openclaw status / openclaw health should work reliably.

Workaround

Install dependencies in extension directories, then restart gateway:

  • For each dist/extensions/*/package.json that declares dependencies, run: 
    npm install --prefix <extension_dir>
  • Restart gateway service(s)
  • Re-run openclaw status / openclaw health

Related issues

  • #61787
  • #69923

This appears to be a regression on 2026.4.21.

extent analysis

TL;DR

Install dependencies in extension directories using npm install --prefix <extension_dir> to resolve MODULE_NOT_FOUND errors and stabilize openclaw status / openclaw health.

Guidance

  • Verify that the issue is specific to OpenClaw version 2026.4.21 by checking if the problem persists in previous versions.
  • Run npm install --prefix <extension_dir> for each extension directory with declared dependencies to ensure all required dependencies are installed.
  • After installing dependencies, restart the gateway service(s) to apply the changes.
  • Re-run openclaw status and openclaw health to confirm that the issue is resolved.

Example

No code snippet is provided as the issue is related to dependency installation and not code-specific.

Notes

This workaround may not be a permanent fix, and the root cause of the regression should be investigated. The issue is specific to OpenClaw version 2026.4.21, and checking related issues (#61787, #69923) may provide more context.

Recommendation

Apply the workaround by installing dependencies in extension directories, as it provides a temporary solution to the problem. This allows for continued use of OpenClaw while a permanent fix is developed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

A fresh supported install should have all required bundled extension runtime dependencies, and openclaw status / openclaw health should work reliably.

#api#agent setup#task chaining#parallel task#integration issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Regression][2026.4.21] npm global install still triggers bundled extension MODULE_NOT_FOUND [2 comments, 3 participants]