openclaw - ✅(Solved) Fix **[Bug]: 2026.4.25 — `chokidar` missing from plugin-runtime-deps bundle; `openclaw memory status` fails with ERR_MODULE_NOT_FOUND after upgrade** [1 pull requests, 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#72882Fetched 2026-04-28 06:30:58
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
4
Author
Timeline (top)
cross-referenced ×3commented ×2closed ×1labeled ×1

After upgrading from 2026.4.24 to 2026.4.25 via openclaw update, the openclaw memory status CLI command fails immediately with:

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'chokidar' imported from
~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63/dist/manager-C6O7HXGc.js
Did you mean to import "chokidar/index.js"?

Running openclaw doctor --fix reports all bundled plugin runtime deps as installed and completes without error, but chokidar is still absent from the plugin-runtime-deps directory after --fix completes:

ls ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63/node_modules/ | grep chokidar
# (no output — chokidar not present)

Error Message

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'chokidar' imported from Running openclaw doctor --fix reports all bundled plugin runtime deps as installed and completes without error, but chokidar is still absent from the plugin-runtime-deps directory after --fix completes: Observe: doctor reports all bundled plugin deps installed, completes without error. Manually installing chokidar inside the plugin-runtime-deps bundle resolves the CLI error:

Root Cause

After upgrading from 2026.4.24 to 2026.4.25 via openclaw update, the openclaw memory status CLI command fails immediately with:

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'chokidar' imported from
~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63/dist/manager-C6O7HXGc.js
Did you mean to import "chokidar/index.js"?

Running openclaw doctor --fix reports all bundled plugin runtime deps as installed and completes without error, but chokidar is still absent from the plugin-runtime-deps directory after --fix completes:

ls ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63/node_modules/ | grep chokidar
# (no output — chokidar not present)

Fix Action

Fix / Workaround

  1. Workaround: cd ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63 npm install chokidar openclaw memory status (now succeeds)
  • openclaw memory status is broken out of the box after upgrade until the manual workaround is applied
  • Gateway and memory plugin function correctly (Telegram responds, memory recall works from agent turns) — this is a CLI-only breakage
  • openclaw doctor --fix does not detect or repair the missing chokidar dep

Workaround

PR fix notes

PR #73207: fix(memory-core): mark plugin enabledByDefault so chokidar runtime dep installs (Fixes #72882)

Description (problem / solution / changelog)

Summary

Fixes openclaw memory status crashing with ERR_MODULE_NOT_FOUND: Cannot find package 'chokidar' after upgrading to 2026.4.25, even after running openclaw doctor --fix.

Root cause

extensions/memory-core/package.json declares chokidar ^5.0.0 (used by manager-sync-ops.ts) as a runtime dependency. The bundled-runtime-deps installer (scanBundledPluginRuntimeDepsisBundledPluginConfiguredForRuntimeDeps) only includes a plugin's deps when:

  • openclaw.plugin.json has enabledByDefault: true, or
  • the user explicitly enables the plugin in plugins.entries, or
  • a configured channel routes through the plugin.

memory-core/openclaw.plugin.json lacked enabledByDefault: true, so on a fresh install the runtime-deps collector silently skipped its dependencies. openclaw memory status is, however, a built-in CLI surface that always loads memory-core — leaving users with a missing chokidar package and a doctor --fix that reports no problems.

The manual workaround the reporter used (npm install chokidar inside the cache) just papered over the missing manifest entry.

Fix

Add "enabledByDefault": true to extensions/memory-core/openclaw.plugin.json. memory-core is a core plugin shipped in every install and exercised by openclaw memory ... regardless of user config, so it should sit in the same default-enabled bucket as the other core extensions (anthropic, bonjour, browser, etc.).

After this change, doctor --fix (and the initial post-install runtime-deps stage) will include chokidar in the plugin-runtime-deps bundle and openclaw memory status will work out of the box.

Test plan

  • Inspect other extensions/*/openclaw.plugin.json core plugins for the existing enabledByDefault: true convention (matched).
  • No code-path change; the behavior is exclusively driven by readBundledPluginRuntimeDepsManifest reading the new field.

Fixes #72882

Changed files

  • extensions/memory-core/openclaw.plugin.json (modified, +1/-0)

Code Example

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'chokidar' imported from
~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63/dist/manager-C6O7HXGc.js
Did you mean to import "chokidar/index.js"?

---

ls ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63/node_modules/ | grep chokidar
# (no output — chokidar not present)

---



---

cd ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63
npm install chokidar
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading from 2026.4.24 to 2026.4.25 via openclaw update, the openclaw memory status CLI command fails immediately with:

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'chokidar' imported from
~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63/dist/manager-C6O7HXGc.js
Did you mean to import "chokidar/index.js"?

Running openclaw doctor --fix reports all bundled plugin runtime deps as installed and completes without error, but chokidar is still absent from the plugin-runtime-deps directory after --fix completes:

ls ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63/node_modules/ | grep chokidar
# (no output — chokidar not present)

Steps to reproduce

  1. Run the upgrade script or openclaw update from 2026.4.24 → 2026.4.25 (npm global install, Linux, node 24.14.1)

  2. After upgrade completes and gateway is running, run: openclaw memory status

  3. Observe ERR_MODULE_NOT_FOUND for chokidar from: ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63/dist/manager-C6O7HXGc.js

  4. Run openclaw doctor --fix Observe: doctor reports all bundled plugin deps installed, completes without error.

  5. Run openclaw memory status again. Observe: same ERR_MODULE_NOT_FOUND — chokidar still missing.

  6. Verify chokidar is absent from the bundle: ls ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63/node_modules/ | grep chokidar (no output)

  7. Workaround: cd ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63 npm install chokidar openclaw memory status (now succeeds)

Expected behavior

openclaw doctor --fix installs chokidar into the plugin-runtime-deps bundle, or the 2026.4.25 package includes it.

Actual behavior

chokidar is absent after both the upgrade and doctor --fix. Manual install inside the bundle directory is the only fix.

OpenClaw version

2026.4.25 (aa36ee6)

Operating system

Linux Mint, linux 6.8.0-110-generic x64, node 24.14.1

Install method

npm global (npm install -g openclaw via openclaw update)

Model

Claude-sonnet-4.5

Provider / routing chain

openrouter

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

  • openclaw memory status is broken out of the box after upgrade until the manual workaround is applied
  • Gateway and memory plugin function correctly (Telegram responds, memory recall works from agent turns) — this is a CLI-only breakage
  • openclaw doctor --fix does not detect or repair the missing chokidar dep

Additional information

Workaround

Manually installing chokidar inside the plugin-runtime-deps bundle resolves the CLI error:

cd ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63
npm install chokidar

After this, openclaw memory status returns correct output and memory is fully operational.

Note: npm install chokidar also removed 425 existing packages from that directory (the bundle had no package.json locking them), so openclaw doctor --fix was run again afterwards to restore the other bundled deps.

Related issues

This appears to be another surface of the bundled plugin runtime dep staging regression tracked in #69842, #67038, #61686. The specific detail here is that chokidar is not included in the deps list that openclaw doctor --fix installs into plugin-runtime-deps, despite being required by dist/manager-C6O7HXGc.js.

extent analysis

TL;DR

Manually installing chokidar in the plugin-runtime-deps bundle resolves the openclaw memory status CLI error.

Guidance

  • The issue is likely caused by a missing dependency chokidar in the plugin-runtime-deps bundle after upgrading to version 2026.4.25.
  • To verify, check if chokidar is present in the node_modules directory of the plugin-runtime-deps bundle using ls ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63/node_modules/ | grep chokidar.
  • To mitigate, manually install chokidar in the bundle directory using cd ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63 followed by npm install chokidar.
  • After manual installation, run openclaw doctor --fix to restore other bundled dependencies.

Example

cd ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-7a0a182eed63
npm install chokidar
openclaw doctor --fix

Notes

This issue appears to be related to a regression in bundled plugin runtime dependency staging, as tracked in #69842, #67038, and #61686. The manual installation of chokidar is a temporary workaround until the underlying issue is resolved.

Recommendation

Apply the workaround by manually installing chokidar in the plugin-runtime-deps bundle, as it is a reliable and immediate solution to the openclaw memory status CLI error.

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

openclaw doctor --fix installs chokidar into the plugin-runtime-deps bundle, or the 2026.4.25 package includes it.

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 - ✅(Solved) Fix **[Bug]: 2026.4.25 — `chokidar` missing from plugin-runtime-deps bundle; `openclaw memory status` fails with ERR_MODULE_NOT_FOUND after upgrade** [1 pull requests, 2 comments, 3 participants]