Plugin fails to load: Cannot find module internal/tslib.js

[changray7]

Bug Description

Plugin fails to load with error: Cannot find module './internal/tslib.js'

Environment

• OpenClaw version: 2026.3.23-2
• Plugin version: 2.0.22
• Node.js environment
• Windows

Steps to Reproduce

1. Install plugin via: openclaw plugins install @supermemory/openclaw-supermemory
2. Add to plugins.allow list
3. Run openclaw plugins list or openclaw status

Error Details

The error occurs when loading the Supermemory SDK:

Error: Cannot find module './internal/tslib.js'
at C:\Users\Administrator.openclaw\extensions\openclaw-supermemory\node_modules\supermemory\client.js

The supermemory package client.js uses require('./internal/tslib.js') but the path resolution fails within the OpenClaw plugin context. The file does exist at node_modules/supermemory/internal/tslib.js.

Expected Behavior

Plugin should load successfully and connect to Supermemory API using the configured API key.

Additional Context

• API Key is configured via SUPERMEMORY_OPENCLAW_API_KEY environment variable
• The tslib module exists at: node_modules/tslib (top level)
• The file node_modules/supermemory/internal/tslib.js does exist but require path resolution seems incorrect

[changray7]

Additional Debug Info

After further investigation, here are the detailed error findings:

Diagnosis

The plugin manifest declares kind: "hook" (I modified it to try to bypass the slot conflict), but the plugin code exports kind: "memory". Even when memory-core is disabled in config, the slot remains occupied.

Config change made:

"plugins": {
  "entries": {
    "memory-core": { "enabled": false },
    "openclaw-supermemory": {
      "enabled": true,
      "config": {
        "apiKey": "${SUPERMEMORY_OPENCLAW_API_KEY}",
        "autoRecall": true,
        "autoCapture": true
      }
    }
  }
}

Error Message

Error: memory slot set to "memory-core"

The system seems to track slot ownership independently from the enabled flag. Disabling memory-core in config doesn't release the slot.

Environment

• OpenClaw: 2026.3.23-2
• Plugin: 2.0.22
• Plugin path: ~\.openclaw\extensions\openclaw-supermemory\
• Node modules: present at ~\.openclaw\extensions\openclaw-supermemory\node_modules\supermemory\

Workaround

If there's a way to force-reset the memory slot allocation, or if the plugin can be updated to use a different slot/key, that would resolve the issue.

[JiwaniZakir]

The require('./internal/tslib.js') call in supermemory/client.js is a relative path that should resolve correctly relative to client.js's own location — the fact that it fails while the file physically exists points to OpenClaw's plugin loader not preserving the correct __dirname for modules loaded within the plugin context. This is a common issue with custom require/vm.runInContext sandboxes that remap module resolution to the host process's directory rather than the plugin's node_modules subtree. The root cause is likely in how OpenClaw wraps or intercepts require when loading extension modules from ~/.openclaw/extensions/, causing relative paths inside transitive dependencies (like supermemory/client.js → ./internal/tslib.js) to be resolved against the wrong base path.