Error: Cannot find module '@larksuiteoapi/node-sdk' Require stack:

• /home/claw/.npm-global/lib/node_modules/openclaw/dist/extensions/feishu/client-yWGpoGkZ.js

Attempting to repair the install with npm install hit a peer dependency conflict, and npm install --legacy-peer-deps then failed in OpenClaw’s postinstall script with:

Error: unsafe dist entry: dist/extensions/amazon-bedrock-mantle/node_modules/.bin/fxparser

So the update path appears to leave the install in a broken state, and the obvious repair path also fails.

Environment

• OpenClaw before update: 2026.4.15 • OpenClaw target version: 2026.4.21 • OS: Linux • Node: v22.22.2 • Install path: /home/claw/.npm-global/lib/node_modules/openclaw

What I ran

Update

openclaw update --yes

This reported:

• Before: 2026.4.15 • After: 2026.4.21

Restart / verify

openclaw gateway restart openclaw status --deep

First failure

openclaw status --deep failed with:

[openclaw] Failed to start CLI: Error: Cannot find module '@larksuiteoapi/node-sdk' Require stack:

• /home/claw/.npm-global/lib/node_modules/openclaw/dist/extensions/feishu/client-yWGpoGkZ.js

Attempted repair

Plain npm install

cd /home/claw/.npm-global/lib/node_modules/openclaw npm install

This failed with ERESOLVE around:

• [email protected] • [email protected] • peerOptional typescript@"^5.4.4"

Legacy peer deps fallback

cd /home/claw/.npm-global/lib/node_modules/openclaw npm install --legacy-peer-deps

This got past the peer conflict, but failed in postinstall:

Error: unsafe dist entry: dist/extensions/amazon-bedrock-mantle/node_modules/.bin/fxparser at listInstalledDistFiles (file:///home/claw/.npm-global/lib/node_modules/openclaw/scripts/postinstall-bundled-plugins.mjs:203:15) at pruneInstalledPackageDist (file:///home/claw/.npm-global/lib/node_modules/openclaw/scripts/postinstall-bundled-plugins.mjs:289:26) at runBundledPluginPostinstall (file:///home/claw/.npm-global/lib/node_modules/openclaw/scripts/postinstall-bundled-plugins.mjs:709:27)

Expected behavior

• openclaw update --yes should leave the install in a working state • openclaw status --deep should run successfully after restart • repair steps should not fail on missing packaged dependencies or postinstall dist-pruning checks

Actual behavior

• update claims success • restart happens • CLI is broken by missing packaged dependency • repair path fails on postinstall script safety check

OpenClaw version

2026.4.21 (f788c88)

Operating system

Linux 6.8.0-110-generic (x64)

Install method

npm global

Model

N/A — failure occurs in CLI/update/install path before model execution

Provider / routing chain

N/A — CLI/update/install failure before provider selection or model routing Configured routing at time of failure: primary anthropic/claude-sonnet-4-6, with fallbacks including openai-codex/gpt-5.4, groq/llama-3.3-70b-versatile, and ollama/qwen2.5-coder:7b.

Additional provider/model setup details

No response

Logs, screenshots, and evidence

TL;DR

The most likely fix is to manually install the missing @larksuiteoapi/node-sdk module and then address the postinstall script issue by removing the unsafe dist entry.

Guidance

• Manually install the missing @larksuiteoapi/node-sdk module using npm install @larksuiteoapi/node-sdk to resolve the initial error.
• Remove the unsafe dist entry dist/extensions/amazon-bedrock-mantle/node_modules/.bin/fxparser to prevent the postinstall script from failing.
• Run npm install --legacy-peer-deps again after addressing the above issues to ensure all dependencies are installed correctly.
• Verify the installation by running openclaw status --deep to ensure the CLI is working as expected.

Example

No specific code snippet is provided as the issue is related to dependency installation and postinstall script errors.

Notes

The provided solution assumes that the missing module and postinstall script issue are the primary causes of the problem. However, there might be other underlying issues that need to be addressed. It's recommended to review the logs and debug files for more information.

Recommendation

Apply the workaround by manually installing the missing module and addressing the postinstall script issue, as the root cause of the problem seems to be related to dependency installation and script errors.