openclaw - 💡(How to fix) Fix Bug: @openclaw/[email protected] package.json has stale extensions/setupEntry pointing to .ts source files [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#77252Fetched 2026-05-05 05:50:42
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
2
Timeline (top)
mentioned ×3subscribed ×3closed ×1commented ×1

Root Cause

The @openclaw/[email protected] npm package package.json still contains stale legacy fields from pre-5.3 that point to non-existent .ts source files:

"openclaw": {
    "extensions": [
      "./index.ts"
    ],
    "setupEntry": "./setup-entry.ts",
    ...
    "runtimeExtensions": [
      "./dist/index.js"
    ],
    "runtimeSetupEntry": "./dist/setup-entry.js"
}

The index.ts and setup-entry.ts files do NOT exist in the published package. Only the compiled dist/ output is shipped.

5.3's source-only plugin scanner reads the old extensions/setupEntry fields, sees .ts source references, and warns that compiled output is required — even though dist/index.js and dist/setup-entry.js exist and are referenced by runtimeExtensions/runtimeSetupEntry.

Fix Action

Workaround

Manually remove lines 30-34 (the extensions and setupEntry fields) from package.json:

"extensions": [
  "./index.ts"
],
"setupEntry": "./setup-entry.ts",

Code Example

plugins: plugin: installed plugin package requires compiled runtime
output for TypeScript entry setup-entry.ts: expected
./dist/setup-entry.js, ...
plugins: plugin: installed plugin package requires compiled runtime
output for TypeScript entry index.ts: expected ./dist/index.js, ...

---

"openclaw": {
    "extensions": [
      "./index.ts"
    ],
    "setupEntry": "./setup-entry.ts",
    ...
    "runtimeExtensions": [
      "./dist/index.js"
    ],
    "runtimeSetupEntry": "./dist/setup-entry.js"
}

---

"extensions": [
  "./index.ts"
],
"setupEntry": "./setup-entry.ts",
RAW_BUFFERClick to expand / collapse

Describe the bug

After upgrading to OpenClaw 2026.5.3, the feishu plugin triggers config warnings:

plugins: plugin: installed plugin package requires compiled runtime
output for TypeScript entry setup-entry.ts: expected
./dist/setup-entry.js, ...
plugins: plugin: installed plugin package requires compiled runtime
output for TypeScript entry index.ts: expected ./dist/index.js, ...

Root cause

The @openclaw/[email protected] npm package package.json still contains stale legacy fields from pre-5.3 that point to non-existent .ts source files:

"openclaw": {
    "extensions": [
      "./index.ts"
    ],
    "setupEntry": "./setup-entry.ts",
    ...
    "runtimeExtensions": [
      "./dist/index.js"
    ],
    "runtimeSetupEntry": "./dist/setup-entry.js"
}

The index.ts and setup-entry.ts files do NOT exist in the published package. Only the compiled dist/ output is shipped.

5.3's source-only plugin scanner reads the old extensions/setupEntry fields, sees .ts source references, and warns that compiled output is required — even though dist/index.js and dist/setup-entry.js exist and are referenced by runtimeExtensions/runtimeSetupEntry.

Steps to reproduce

  1. Install OpenClaw 2026.5.3
  2. Install @openclaw/[email protected]
  3. Run openclaw doctor
  4. Observe config warnings about setup-entry.ts and index.ts

Expected behavior

No config warnings. The plugin should load using runtimeExtensions/runtimeSetupEntry.

Workaround

Manually remove lines 30-34 (the extensions and setupEntry fields) from package.json:

"extensions": [
  "./index.ts"
],
"setupEntry": "./setup-entry.ts",

Actual fix

The @openclaw/feishu build/publish pipeline should strip the legacy extensions and setupEntry fields when runtimeExtensions/runtimeSetupEntry are present, or use a build script to remove them before publishing.

Related

  • Same bug pattern as #77044 (Discord plugin had identical issue, already fixed)

extent analysis

TL;DR

Manually removing the legacy extensions and setupEntry fields from the @openclaw/feishu package's package.json file may resolve the config warnings.

Guidance

  • Verify that the dist/index.js and dist/setup-entry.js files exist in the published package and are correctly referenced by runtimeExtensions and runtimeSetupEntry.
  • Remove the extensions and setupEntry fields from the package.json file as a temporary workaround.
  • Check if the issue is resolved after applying the workaround by running openclaw doctor again.
  • Consider reaching out to the maintainers of the @openclaw/feishu package to report the issue and suggest a permanent fix, such as updating the build/publish pipeline to strip the legacy fields.

Example

No code snippet is necessary in this case, as the issue can be resolved through configuration changes.

Notes

This workaround may not be suitable for all users, especially if they are not comfortable modifying the package's package.json file. A permanent fix from the package maintainers is recommended.

Recommendation

Apply the workaround by manually removing the legacy fields, as this is a simple and effective solution to resolve the config warnings.

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

No config warnings. The plugin should load using runtimeExtensions/runtimeSetupEntry.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING