Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix memory-lancedb npm v2026.5.3: imports nonexistent subpath `openclaw/plugin-sdk/plugin-config-runtime` — plugin fails to load [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#77673•Fetched 2026-05-06 06:23:14
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Author
ndagle73ndagle73
Participants
clawsweeper[bot]clawsweeper[bot]ndagle73ndagle73
Timeline (top)
closed ×1commented ×1

Error Message

[plugins] memory-lancedb failed to load from /sandbox/.openclaw/npm/node_modules/@openclaw/memory-lancedb/dist/index.js: Error: Cannot find module '/usr/local/lib/node_modules/openclaw/dist/plugin-sdk/root-alias.cjs/plugin-config-runtime' Require stack:

  • /sandbox/.openclaw/npm/node_modules/@openclaw/memory-lancedb/dist/index.js

Root Cause

The npm-published dist/index.js imports:

import { resolveLivePluginConfigObject } from "openclaw/plugin-sdk/plugin-config-runtime";

But the corresponding subpath plugin-config-runtime does not exist in OpenClaw 2026.5.3-1's dist/plugin-sdk/ tree. The function resolveLivePluginConfigObject IS exported from other subpath files (memory-core.js, compat.js, memory-core-host-runtime-core.js, etc.) but not from a file named plugin-config-runtime.

Source code in the OpenClaw repo at packages/plugin-sdk/src/ has config-runtime.ts (no plugin- prefix) — so it appears the npm package's bundle was built with an import path that doesn't match the published exports map / subpath structure.

Fix Action

Workaround

Use the bundled plugin (/usr/local/lib/node_modules/openclaw/dist/extensions/memory-lancedb/, version 2026.4.20) instead by removing plugins.allow and plugins.load.paths from openclaw.json. The bundled plugin uses a content-hashed relative import (../../config-runtime-Dutm3Ah0.js) that resolves correctly.

Code Example

[plugins] memory-lancedb failed to load from /sandbox/.openclaw/npm/node_modules/@openclaw/memory-lancedb/dist/index.js: Error: Cannot find module '/usr/local/lib/node_modules/openclaw/dist/plugin-sdk/root-alias.cjs/plugin-config-runtime'
Require stack:
- /sandbox/.openclaw/npm/node_modules/@openclaw/memory-lancedb/dist/index.js

---

import { resolveLivePluginConfigObject } from "openclaw/plugin-sdk/plugin-config-runtime";

---

# clean pod, openclaw 2026.5.3-1
openclaw plugins install @openclaw/memory-lancedb
openclaw config set plugins.slots.memory memory-lancedb
openclaw config set 'plugins.allow' '["memory-lancedb"]' --json
openclaw config set 'plugins.load.paths' '["/sandbox/.openclaw/npm/node_modules/@openclaw/memory-lancedb"]' --json
# restart gateway, observe load failure in gateway log
RAW_BUFFERClick to expand / collapse

Bug

@openclaw/[email protected] (npm) fails to load on OpenClaw 2026.5.3-1 with:

[plugins] memory-lancedb failed to load from /sandbox/.openclaw/npm/node_modules/@openclaw/memory-lancedb/dist/index.js: Error: Cannot find module '/usr/local/lib/node_modules/openclaw/dist/plugin-sdk/root-alias.cjs/plugin-config-runtime'
Require stack:
- /sandbox/.openclaw/npm/node_modules/@openclaw/memory-lancedb/dist/index.js

Root cause

The npm-published dist/index.js imports:

import { resolveLivePluginConfigObject } from "openclaw/plugin-sdk/plugin-config-runtime";

But the corresponding subpath plugin-config-runtime does not exist in OpenClaw 2026.5.3-1's dist/plugin-sdk/ tree. The function resolveLivePluginConfigObject IS exported from other subpath files (memory-core.js, compat.js, memory-core-host-runtime-core.js, etc.) but not from a file named plugin-config-runtime.

Source code in the OpenClaw repo at packages/plugin-sdk/src/ has config-runtime.ts (no plugin- prefix) — so it appears the npm package's bundle was built with an import path that doesn't match the published exports map / subpath structure.

Reproduction

# clean pod, openclaw 2026.5.3-1
openclaw plugins install @openclaw/memory-lancedb
openclaw config set plugins.slots.memory memory-lancedb
openclaw config set 'plugins.allow' '["memory-lancedb"]' --json
openclaw config set 'plugins.load.paths' '["/sandbox/.openclaw/npm/node_modules/@openclaw/memory-lancedb"]' --json
# restart gateway, observe load failure in gateway log

Workaround

Use the bundled plugin (/usr/local/lib/node_modules/openclaw/dist/extensions/memory-lancedb/, version 2026.4.20) instead by removing plugins.allow and plugins.load.paths from openclaw.json. The bundled plugin uses a content-hashed relative import (../../config-runtime-Dutm3Ah0.js) that resolves correctly.

Suggested fix

Either:

  • Republish @openclaw/memory-lancedb with the import path that matches the published subpath layout (e.g. openclaw/plugin-sdk/memory-core or whichever subpath canonically exports resolveLivePluginConfigObject)
  • Or add a plugin-config-runtime re-export subpath to OpenClaw's dist/plugin-sdk/ so the existing npm bundle resolves

Environment

  • OpenClaw 2026.5.3-1
  • @openclaw/memory-lancedb 2026.5.3 (npm)
  • macOS 26.4 + Docker Desktop / openshell-cluster-nemoclaw
  • pod runs as gateway uid 999 (gosu drop fallback to root in OpenShell no-new-privileges container; structural)

extent analysis

TL;DR

The most likely fix is to republish @openclaw/memory-lancedb with the correct import path or add a plugin-config-runtime re-export subpath to OpenClaw's dist/plugin-sdk/.

Guidance

  • Verify the import path in @openclaw/memory-lancedb's dist/index.js to ensure it matches the published subpath layout.
  • Check the OpenClaw repository's packages/plugin-sdk/src/ for the correct export path of resolveLivePluginConfigObject.
  • Consider using the bundled plugin as a temporary workaround by removing plugins.allow and plugins.load.paths from openclaw.json.
  • Review the reproduction steps to ensure the issue is consistently reproducible.

Example

No code snippet is provided as the issue is related to the import path and subpath structure.

Notes

The suggested fix assumes that the issue is due to the mismatch between the import path in @openclaw/memory-lancedb and the published subpath layout in OpenClaw. If this is not the case, further investigation may be required.

Recommendation

Apply the workaround by using the bundled plugin until the @openclaw/memory-lancedb package is republished with the correct import path or the plugin-config-runtime re-export subpath is added to OpenClaw's dist/plugin-sdk/. This is because the workaround is a simpler and more immediate solution that can mitigate the issue until a permanent fix is available.

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…
#LLM response#prompt template#agent execution#callback error#memory management

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 memory-lancedb npm v2026.5.3: imports nonexistent subpath `openclaw/plugin-sdk/plugin-config-runtime` — plugin fails to load [1 comments, 2 participants]