Summary

After upgrading to openclaw 2026.3.7, the BlueBubbles plugin no longer loads.

Gateway log error:

[plugins] bluebubbles failed to load from /opt/homebrew/lib/node_modules/openclaw/extensions/bluebubbles/index.ts:
Error: Cannot find module '../../../src/infra/parse-finite-number.js'
Require stack:
- /opt/homebrew/lib/node_modules/openclaw/extensions/bluebubbles/src/monitor-normalize.ts

Environment

• OpenClaw: 2026.3.7
• Install method: global npm install (/opt/homebrew/lib/node_modules/openclaw)
• OS: macOS (arm64)
• Node: v25.6.1

Reproduction

1. npm install -g [email protected]
2. Enable BlueBubbles plugin (plugins.entries.bluebubbles.enabled=true)
3. Start/restart Gateway
4. Plugin loader repeatedly logs the Cannot find module error above (roughly every 10s)

Analysis

In:

/opt/homebrew/lib/node_modules/openclaw/extensions/bluebubbles/src/monitor-normalize.ts

line 1 imports:

import { parseFiniteNumber } from "../../../src/infra/parse-finite-number.js";

That target does not exist in the published npm install:

• missing: /opt/homebrew/lib/node_modules/openclaw/src/infra/parse-finite-number.js
• present are dist artifacts (including hashed bundles and dist/plugin-sdk/...d.ts)

So this appears to be a runtime import path / packaging bug (extension imports from src/... not present at runtime), not a local config/dependency issue.

Expected behavior

BlueBubbles should load normally on 2026.3.7 without repeated loader errors.

Actual behavior

BlueBubbles fails to load, channel functionality is unavailable, and logs are spammed.

Workaround

• Disable plugin (plugins.entries.bluebubbles.enabled=false) or
• Roll back to an earlier version

Additional note

A similar import pattern (../../../../src/infra/parse-finite-number.js) is visible in the Mattermost plugin source as well. This may indicate a broader packaging issue for extension runtime imports pointing to src/....