Description

After upgrading to OpenClaw 2026.5.3-1, a new config warning appears on every gateway restart:

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

Root Cause

The installed plugin @tencent-weixin/openclaw-weixin@2.3.1 declares its entry point as ./index.ts in openclaw.plugin.json, but the published npm package contains no compiled output (dist/ directory does not exist) and no tsconfig.json. As a result, the plugin cannot be built locally either.

The package's package.json has a build script (tsc) and prepublishOnly that should run it, but the compiled output was not included in the published package.

Impact

• Warning appears on every gateway restart
• No actionable fix path for end users — the plugin cannot be built locally due to missing tsconfig.json
• The plugin's source repository is not publicly available (no repository field in package.json)

Suggested Improvements

1. When OpenClaw detects a TypeScript plugin entry with no compiled output, provide a clear error message explaining the issue is with the plugin publisher, not the user's configuration
2. Consider validating compiled output exists during plugin installation (openclaw plugins install) rather than at gateway startup
3. Document the requirement for plugin authors to include compiled output in published packages

Environment

• OpenClaw: 2026.5.3-1 (2eae30e)
• OS: macOS 26.4.1 (arm64)
• Node: 24.15.0
• Plugin: @tencent-weixin/openclaw-weixin@2.3.1
• Install method: npm global