openclaw - 💡(How to fix) Fix [Windows] Feishu channel crashes with ESM path error [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#73509Fetched 2026-04-29 06:19:02
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×2closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

环境

  • OS: Windows
  • OpenClaw 版本: 2026.4.24
  • 飞书插件: 内置版本

问题描述

飞书频道一直崩溃重启,无法正常工作。

错误日志

Steps to reproduce

[feishu] [default] channel exited: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:' [feishu] [default] auto-restart attempt 1/10 in 5s [feishu] [default] channel exited: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:' ... (持续崩溃重启)

Expected behavior

重现步骤

  1. 在 Windows 上启动 OpenClaw Gateway
  2. 飞书频道自动加载
  3. 飞书立即崩溃并无限重启

初步分析

问题出在飞书插件内部使用 ESM 加载模块时,将 Windows 路径 (如 C:\Users\...) 直接传给了 import() 函数,但 Node.js ESM 要求 Windows 路径必须写成 file:///C:/... 格式。

Actual behavior

飞书频道一直崩溃重启,无法正常接收消息。Gateway 启动成功后飞书插件立即崩溃,每隔几秒尝试重启一次,无限循环。

OpenClaw version

2026.4.24

Operating system

Windows 10

Install method

npm install -g openclaw,然后 openclaw gateway 启动

Model

minimax/MiniMax-M2.7

Provider / routing chain

minimax (api.minimaxi.com)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can be fixed by modifying the file path in the ESM loader to use the file:/// scheme for Windows paths.

Guidance

  • The error message indicates that the ESM loader only supports URLs with schemes file, data, and node, and Windows paths must be valid file:// URLs.
  • To fix the issue, the code should be updated to convert Windows paths to the correct file:/// format before passing them to the import() function.
  • The c: protocol in the error message suggests that the code is currently passing an absolute Windows path directly to the import() function, which is causing the error.
  • The fix may involve using a library or function to normalize the file paths and convert them to the correct format for the ESM loader.

Example

const filePath = 'C:\\\\\\Users\\\\\\...';
const normalizedPath = `file:///${filePath.replace(/\\/g, '/')}`;
import(normalizedPath);

Notes

The exact fix will depend on the specific code and implementation, but the general approach should involve normalizing the file paths and converting them to the correct format for the ESM loader.

Recommendation

Apply workaround: The issue can be fixed by modifying the code to correctly handle Windows paths and convert them to the file:/// format. This will allow the ESM loader to load the modules correctly and prevent the crashes.

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