openclaw - 💡(How to fix) Fix [Bug]: Docker build fails due to unresolved import channel-policy.js in Google Chat extension. [4 comments, 4 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#49455Fetched 2026-04-08 00:55:05
View on GitHub
Comments
4
Participants
4
Timeline
10
Reactions
1
Timeline (top)
commented ×4labeled ×2closed ×1locked ×1

Docker build fails due to unresolved import channel-policy.js in Google Chat extension.

Error Message

Build fails with unresolved import error: Error originates from:

Root Cause

Docker build fails due to unresolved import channel-policy.js in Google Chat extension.

Code Example

The file src/channels/channel-policy.ts (or .js) does not exist in the repository.

However, it is still being imported in:

extensions/googlechat/runtime-api.ts

This causes the build to fail during bundling (rolldown / tsdown).

Local verification:

ls src/channels/channel-policy.*
# -> no matches found
RAW_BUFFERClick to expand / collapse

Bug type

Crash (process/app exits or hangs)

Summary

Docker build fails due to unresolved import channel-policy.js in Google Chat extension.

Steps to reproduce

Clone the latest OpenClaw repository

Run:

./docker-setup.sh

or manually:

docker build -t openclaw:local .

Build fails at:

pnpm build:docker

Expected behavior

The Docker image should build successfully without module resolution errors.

Actual behavior

Build fails with unresolved import error:

[UNRESOLVED_IMPORT] Could not resolve '../../src/channels/channel-policy.js'

Error originates from:

extensions/googlechat/runtime-api.ts

OpenClaw version

2026.3.14 (Docker build from latest repo)

Operating system

macOS (Apple Silicon)

Install method

No response

Model

none

Provider / routing chain

none

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

The file src/channels/channel-policy.ts (or .js) does not exist in the repository.

However, it is still being imported in:

extensions/googlechat/runtime-api.ts

This causes the build to fail during bundling (rolldown / tsdown).

Local verification:

ls src/channels/channel-policy.*
# -> no matches found

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To resolve the issue, we need to either create the missing channel-policy.js file or update the import statement in runtime-api.ts to point to the correct location of the file.

Here are the steps:

  • Check if channel-policy.ts or channel-policy.js exists in the repository and update the import statement accordingly.
  • If the file does not exist, create it in the correct location (src/channels/) or remove the import statement if it's not needed.

Example code update in extensions/googlechat/runtime-api.ts:

// Before
import '../../src/channels/channel-policy.js';

// After (if channel-policy.ts exists)
import '../../src/channels/channel-policy';

Alternatively, if channel-policy.js is supposed to be generated during the build process, ensure that the build script is correctly configured to generate this file.

Verification

To verify that the fix worked, run the Docker build command again:

docker build -t openclaw:local .

If the build is successful, the issue is resolved.

Extra Tips

  • Ensure that the file path in the import statement is correct and relative to the current file.
  • If using a bundler like Rollup, check the configuration to ensure that it's correctly handling the import statements.
  • Use a linter or code analyzer to detect and prevent similar issues in the future.

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…

FAQ

Expected behavior

The Docker image should build successfully without module resolution errors.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING