openclaw - 💡(How to fix) Fix Bundled channel package exports missing require/default entries (CommonJS) [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#72233Fetched 2026-04-27 05:32:52
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
Timeline (top)
closed ×1commented ×1

Several bundled channel packages have \package.json\ exports fields that don't expose CommonJS-compatible entry points, causing failures when OpenClaw resolves them via CommonJS:

\
failed to load bundled channel imessage: No "" main defined ... @mariozechner/pi-coding-agent/package.json failed to load bundled channel irc: No "" main defined ... @mariozechner/pi-coding-agent/package.json failed to load bundled channel mattermost: No "" main defined ... osc-progress/package.json failed to load bundled channel signal: Package subpath './oauth' is not defined by "" ... @mariozechner/pi-ai/package.json \\

Root Cause

Several bundled channel packages have \package.json\ exports fields that don't expose CommonJS-compatible entry points, causing failures when OpenClaw resolves them via CommonJS:

\
failed to load bundled channel imessage: No "" main defined ... @mariozechner/pi-coding-agent/package.json failed to load bundled channel irc: No "" main defined ... @mariozechner/pi-coding-agent/package.json failed to load bundled channel mattermost: No "" main defined ... osc-progress/package.json failed to load bundled channel signal: Package subpath './oauth' is not defined by "" ... @mariozechner/pi-ai/package.json \\

Fix Action

Fix / Workaround

Local fix applied

Patched \package.json\ exports in each package to add \default\ and
equire\ entries.

RAW_BUFFERClick to expand / collapse

Environment

  • Windows 10, Node v22.22.0, OpenClaw 2026.4.24

Description

Several bundled channel packages have \package.json\ exports fields that don't expose CommonJS-compatible entry points, causing failures when OpenClaw resolves them via CommonJS:

\
failed to load bundled channel imessage: No "" main defined ... @mariozechner/pi-coding-agent/package.json failed to load bundled channel irc: No "" main defined ... @mariozechner/pi-coding-agent/package.json failed to load bundled channel mattermost: No "" main defined ... osc-progress/package.json failed to load bundled channel signal: Package subpath './oauth' is not defined by "" ... @mariozechner/pi-ai/package.json \\

Affected packages

  • @mariozechner/pi-coding-agent\ — missing \default/
    equire\ in exports
  • @mariozechner/pi-ai\ — missing ./oauth\ subpath export
  • \osc-progress\ — missing \default/
    equire\ in exports

Impact

Channels imessage, irc, mattermost, signal, msteams, tlon all fail to load.

Local fix applied

Patched \package.json\ exports in each package to add \default\ and
equire\ entries.

extent analysis

TL;DR

Update the exports field in the package.json files of affected packages to include CommonJS-compatible entry points.

Guidance

  • Verify that the exports field in the package.json files of the affected packages (@mariozechner/pi-coding-agent, @mariozechner/pi-ai, and osc-progress) includes the necessary default and require entries.
  • Check the OpenClaw documentation to ensure that the exports field is correctly formatted for CommonJS compatibility.
  • Apply the local fix that was applied to the package.json files, which added default and require entries to the exports field.
  • Test the updated packages to ensure that the channels can be loaded successfully.

Example

{
  "exports": {
    ".": {
      "default": "./index.js",
      "require": "./index.cjs"
    }
  }
}

Notes

The fix may not apply to all versions of OpenClaw or Node.js, and additional configuration may be required for specific use cases.

Recommendation

Apply the workaround by updating the exports field in the package.json files of the affected packages, as this is a targeted fix that addresses the specific issue described.

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