Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: ESM import of chokidar fails in plugin runtime deps, causing embeddings "not ready" [1 comments, 2 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#73819•Fetched 2026-04-29 06:14:41
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
taigoiltaigoil
Participants
clawsweeper[bot]clawsweeper[bot]taigoiltaigoil
Timeline (top)
closed ×1commented ×1labeled ×1

The chokidar package files exist in node_modules/chokidar/, but the bare ESM specifier import { watch } from 'chokidar' fails to resolve. The module loader suggests chokidar/index.js instead.

This causes the entire memory manager module to fail to load, preventing embeddings from initializing even though the embedding provider is fully functional.

Error Message

  1. Observe the error about chokidar import and embeddings not ready

Root Cause

The chokidar package files exist in node_modules/chokidar/, but the bare ESM specifier import { watch } from 'chokidar' fails to resolve. The module loader suggests chokidar/index.js instead.

This causes the entire memory manager module to fail to load, preventing embeddings from initializing even though the embedding provider is fully functional.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

The chokidar package files exist in node_modules/chokidar/, but the bare ESM specifier import { watch } from 'chokidar' fails to resolve. The module loader suggests chokidar/index.js instead.

This causes the entire memory manager module to fail to load, preventing embeddings from initializing even though the embedding provider is fully functional.

Steps to reproduce

  1. Install OpenClaw 2026.4.26
  2. Configure agents.defaults.memorySearch.provider as "ollama" with model "bge-m3"
  3. Run openclaw doctor or openclaw memory status --deep
  4. Observe the error about chokidar import and embeddings not ready

Expected behavior

  • The chokidar package should be imported correctly
  • The memory manager should initialize successfully
  • Embeddings should report as ready when Ollama is running and the model is available

Actual behavior

Two errors appear:

Cannot find package 'chokidar' imported from /home/davidd/.openclaw/plugin-runtime-deps/openclaw-2026.4.26-ff1bc86c1139/dist/manager-ICKYl3BU.js Did you mean to import "chokidar/index.js"?

Memory search provider "ollama" is configured, but the gateway reports embeddings are not ready. Gateway memory probe for default agent is not ready: Cannot find package 'chokidar'...

OpenClaw version

OpenClaw 2026.4.26-ff1bc86c1139

Operating system

  • Linux 6.17.0-22-generic (x64) | Node.js v22.22.2

Install method

npm global

Model

Ollama in Docker, port 11434, bge-m3:latest installed

Provider / routing chain

openclaw - docker ollama

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can be resolved by using the correct import path for the chokidar package, likely due to a change in the package's export structure.

Guidance

  • Verify that the chokidar package is installed correctly by checking the node_modules/chokidar directory.
  • Try importing chokidar using the suggested path chokidar/index.js instead of the bare ESM specifier.
  • Check the chokidar package documentation to see if there have been any changes to the export structure that could be causing the issue.
  • Consider updating the chokidar package to the latest version to ensure compatibility with the current Node.js version.

Example

// Instead of
import { watch } from 'chokidar';

// Try
import { watch } from 'chokidar/index.js';

Notes

The issue may be specific to the OpenClaw version 2026.4.26-ff1bc86c1139 and the chokidar package version being used. Further investigation into the package versions and export structures may be necessary to determine the root cause.

Recommendation

Apply workaround: Use the suggested import path chokidar/index.js to resolve the issue, as the bare ESM specifier is not working as expected.

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

  • The chokidar package should be imported correctly
  • The memory manager should initialize successfully
  • Embeddings should report as ready when Ollama is running and the model is available
#index setup#retrieval issue#search optimization#API routing#API middleware

Still need to ship something?

×6

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

Back to top recommendations

TRENDING