Why does OpenClaw v2026.4.21 installation fail?

The npm package for v2026.4.21 is missing the @larksuiteoapi/node-sdk dependency and nostr-tools. npm install then fails in postinstall on an unsafe dist entry for fxparser.

How to fix broken OpenClaw v2026.4.21 install?

Wait for a patch release or manually install the missing dependencies. The issue is a package publishing problem where extension dependencies are not included in the npm release.

When will OpenClaw fix the v2026.4.21 npm issue?

The issue was filed April 23, 2026 and tagged as a regression/bug. A patch is expected in a subsequent release.

Does the v2026.4.21 bug affect fresh installations?

Yes. Both upgrades from v2026.4.15 and fresh npm install -g openclaw@latest are affected (issue #70457).

What error do I see with broken OpenClaw v2026.4.21?

openclaw status --deep fails with 'Cannot find module @larksuiteoapi/node-sdk', and npm install --legacy-peer-deps fails in postinstall on an unsafe dist entry under dist/extensions/amazon-bedrock-mantle/node_modules/.bin/fxparser.

← Back to dashboard

clawsmith.com/signal/openclaw-v2026-4-21-npm-larksuiteoapi-broken-install

⚠ IssueWide OpenLive

OpenClaw v2026.4.21 update leaves broken install: missing @larksuiteoapi/node-sdk and postinstall failure

Upgrading from v2026.4.15 to v2026.4.21 leaves installations broken. openclaw status --deep fails with missing @larksuiteoapi/node-sdk module. npm install then fails in postinstall on unsafe dist entry for fxparser. Fresh installs also affected (issue #70457). Package publishing issue where extension dependencies not included in npm release.

Product Idea from this Signal

A CLI wrapper that safely updates OpenClaw by backing up state, stopping services, running the update, and restoring on failure

71 ▲

Running openclaw update on a production instance destroys the running gateway, corrupts channel configs (Feishu, Telegram), and permanently deletes all cron jobs because npm install runs without stopping the LaunchAgent first. GitHub issue #66401 documented the 100% reproducible cascading failure. Multiple related issues (#62051, #42883, #37605) show this is a systemic pattern across versions. This tool wraps the update process with pre-flight checks, automatic state backup, graceful service shutdown, and rollback on failure.

CLIOPEN-SOURCEDEVOPSRELIABILITY

UnderservedView Opportunity →

Product Idea from this Signal

A CLI tool that snapshots your OpenClaw state before updates, runs the upgrade in a sandboxed dry-run against your live config, and auto-rolls back if any health check fails

433.6k ▲

OpenClaw ships updates every 2-3 days and each one risks breaking exec permissions, crashing the gateway, saturating CPU with plugin loading bugs, or silently deleting cron jobs. Four separate regressions in April 2026 alone (v2026.4.1 sandbox, v2026.4.5 CPU, v2026.4.14 memory timeouts, update command wiping Feishu and crons) hit thousands of self-hosters with no rollback path. The built-in openclaw doctor only validates config schema after the fact. This tool wraps the entire update lifecycle: snapshot state, dry-run the upgrade against your actual agent/cron/channel config, diff the before/after, and block or auto-rollback if anything regresses.

CLIOPEN-SOURCEDEVTOOLSELF-HOSTEDRELIABILITY

CompetitiveView Opportunity →