Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Bug: [email protected] npm package is incomplete (missing extensions/runtime-api files) [1 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#59131•Fetched 2026-04-08 02:28:18
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
BenSHPDBenSHPD
Participants
BenSHPDBenSHPD

The published npm package [email protected] appears incomplete. A clean install still results in missing files under packages/extensions, and npm pack [email protected] confirms the tarball itself does not contain them.

Root Cause

The published npm package [email protected] appears incomplete. A clean install still results in missing files under packages/extensions, and npm pack [email protected] confirms the tarball itself does not contain them.

Code Example

tmpdir=$(mktemp -d)
cd "$tmpdir"
npm pack openclaw@2026.3.28
mkdir unpack
tar -xzf openclaw-2026.3.28.tgz -C unpack
RAW_BUFFERClick to expand / collapse

Summary

The published npm package [email protected] appears incomplete. A clean install still results in missing files under packages/extensions, and npm pack [email protected] confirms the tarball itself does not contain them.

What I checked

After reinstalling globally, the local install still missed these files:

  • packages/extensions/image-generation-core/runtime-api.js
  • packages/extensions/diffs/runtime-api.js
  • packages/extensions/image-generation-core/package.json
  • packages/extensions/diffs/package.json
  • packages/extensions/deepgram/package.json
  • packages/extensions/deepseek/package.json
  • packages/extensions/groq/package.json

To distinguish local corruption from a bad published artifact, I ran npm pack [email protected], unpacked the tarball, and checked the same paths there. The same files are missing from the tarball itself.

Impact

This means users can reinstall 2026.3.28 cleanly and still end up with an incomplete runtime tree, making rollback / recovery from later regressions unreliable.

Repro

tmpdir=$(mktemp -d)
cd "$tmpdir"
npm pack [email protected]
mkdir unpack
tar -xzf openclaw-2026.3.28.tgz -C unpack

Then verify these paths are absent under unpack/package/packages/extensions/.

Expected

The published npm package for 2026.3.28 should contain a complete runtime tree matching what the CLI expects at runtime.

Actual

The published tarball is missing multiple extension/runtime files.

extent analysis

TL;DR

The missing files in the [email protected] npm package can be addressed by republishing the package with the complete runtime tree.

Guidance

  • Verify the package build process to ensure all necessary files are included in the tarball.
  • Check the package.json file for any scripts or configurations that might be excluding the missing files during the build process.
  • Run the repro steps provided to confirm the issue and test any potential fixes.
  • Consider publishing a new version of the package with the complete runtime tree to ensure reliable rollback and recovery.

Example

No code snippet is provided as the issue is related to the packaging process rather than code implementation.

Notes

The issue seems to be related to the packaging process, and republishing the package with the complete runtime tree should resolve the issue. However, without more information about the build process, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Republish the openclaw package with the complete runtime tree to ensure reliable rollback and recovery. This is necessary because the current published package is incomplete, and republishing will provide a reliable way to recover from later regressions.

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…
#api#serialization error#model compatibility#GPU setup#container setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING