openclaw - 💡(How to fix) Fix [Bug] Telegram channel setup-entry.js references missing ./src/channel.setup.js in v2026.4.7 [3 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

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#62915Fetched 2026-04-09 08:00:45
View on GitHub
Comments
3
Participants
4
Timeline
3
Reactions
1
Author
Timeline (top)
commented ×3

Error Message

After upgrading to 2026.4.7, OpenClaw fails to start / config loading throws an error because the Telegram extension's setup-entry.js references a path that doesn't exist in the built package:

Root Cause

dist/extensions/telegram/setup-entry.js references:

plugin: { specifier: "./src/channel.setup.js", exportName: "telegramSetupPlugin" }

But the src/ subdirectory does not exist in the built package. The actual chunk is at dist/channel.setup-DnkdT607.js.

Fix Action

Temporary Workaround

Manually create the missing bridge file:

mkdir -p /opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src
cat > /opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js << 'EOF'
import { t as telegramSetupPlugin } from "../../../channel.setup-DnkdT607.js";
export { telegramSetupPlugin };
EOF

⚠️ This workaround will be overwritten on next update.

Code Example

bundled plugin entry "./src/channel.setup.js" failed to open

---

plugin: { specifier: "./src/channel.setup.js", exportName: "telegramSetupPlugin" }

---

plugin: { specifier: "./setup-plugin-api.js", exportName: "whatsappSetupPlugin" }

---

import { t as whatsappSetupPlugin } from "../../channel.setup-DCi4EAZK.js";
export { whatsappSetupPlugin };

---

mkdir -p /opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src
cat > /opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js << 'EOF'
import { t as telegramSetupPlugin } from "../../../channel.setup-DnkdT607.js";
export { telegramSetupPlugin };
EOF
RAW_BUFFERClick to expand / collapse

Environment

  • OpenClaw version: 2026.4.7 (5050017)
  • OS: macOS (arm64)
  • Install method: npm -g

Problem

After upgrading to 2026.4.7, OpenClaw fails to start / config loading throws an error because the Telegram extension's setup-entry.js references a path that doesn't exist in the built package:

bundled plugin entry "./src/channel.setup.js" failed to open

Root Cause

dist/extensions/telegram/setup-entry.js references:

plugin: { specifier: "./src/channel.setup.js", exportName: "telegramSetupPlugin" }

But the src/ subdirectory does not exist in the built package. The actual chunk is at dist/channel.setup-DnkdT607.js.

Comparison with WhatsApp (works correctly)

dist/extensions/whatsapp/setup-entry.js correctly references:

plugin: { specifier: "./setup-plugin-api.js", exportName: "whatsappSetupPlugin" }

And dist/extensions/whatsapp/setup-plugin-api.js exists as a bridge file:

import { t as whatsappSetupPlugin } from "../../channel.setup-DCi4EAZK.js";
export { whatsappSetupPlugin };

Telegram is missing the equivalent bridge file. dist/extensions/telegram/setup-plugin-api.js (or equivalent) was not generated during the build.

Temporary Workaround

Manually create the missing bridge file:

mkdir -p /opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src
cat > /opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js << 'EOF'
import { t as telegramSetupPlugin } from "../../../channel.setup-DnkdT607.js";
export { telegramSetupPlugin };
EOF

⚠️ This workaround will be overwritten on next update.

Expected Fix

The build process should generate dist/extensions/telegram/setup-plugin-api.js (matching the WhatsApp pattern), and update setup-entry.js to reference ./setup-plugin-api.js — consistent with all other channel extensions.

extent analysis

TL;DR

Create a bridge file setup-plugin-api.js in the Telegram extension directory to fix the missing reference issue.

Guidance

  • Verify the build process is correctly generating bridge files for other extensions, such as WhatsApp, to ensure consistency.
  • Check the build configuration for the Telegram extension to identify why the bridge file is not being generated.
  • Apply the temporary workaround provided, but be aware it will be overwritten on the next update.
  • Consider updating the build process to generate the missing bridge file setup-plugin-api.js for the Telegram extension.

Example

// dist/extensions/telegram/setup-plugin-api.js
import { t as telegramSetupPlugin } from "../../../channel.setup-DnkdT607.js";
export { telegramSetupPlugin };

Notes

The provided temporary workaround is not a permanent solution, as it will be overwritten on the next update. A more robust fix would involve updating the build process to generate the missing bridge file.

Recommendation

Apply the workaround, but prioritize updating the build process to generate the missing bridge file setup-plugin-api.js for a permanent fix, as this will ensure consistency with other extensions and prevent future issues.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING