PR #60112: build: fix plugin shared chunk routing to preserve node_modules resolution

• Repository: openclaw/openclaw
• Author: medns
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/60112

Description (problem / solution / changelog)

Summary

• Problem: tsdown code-splitting hoists shared chunks to the root dist/ directory, breaking Node.js module resolution for bundled plugins (like Slack) that rely on their own isolated node_modules.
• Why it matters: This causes a fatal MODULE_NOT_FOUND error at runtime for any plugin that uses shared internal code and external dependencies, completely breaking the Slack integration in v2026.4.2.
• What changed: Injected a custom chunkFileNames output option in tsdown.config.ts. It analyzes the source files of each chunk; if a chunk exclusively belongs to a single plugin, it routes the output back to that plugin's dist/extensions/<id>/ directory.
• What did NOT change (scope boundary): Core chunk routing and cross-plugin violation chunks still fallback to the root dist/ directory.

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #60004
• Related #
• This PR fixes a bug or regression

Root Cause / Regression History (if applicable)

• Root cause: The bundler (tsdown/rolldown) extracts shared code within a plugin into a common chunk and outputs it to the root dist/ folder by default. This strips the plugin's physical directory context, preventing Node from finding the plugin's private node_modules.
• Missing detection / guardrail: The build process did not verify if the generated chunks maintained their expected directory structure for module resolution.
• Prior context (git blame, prior PR, issue, or refactor if known): N/A
• Why this regressed now: Likely due to a recent update in how plugins are bundled or a migration to tsdown.
• If unknown, what was ruled out: N/A

Regression Test Plan (if applicable)

• Coverage level that should have caught this:
  • Unit test
  • Seam / integration test
  • End-to-end test
  • Existing coverage already sufficient
• Target test or file: src/infra/tsdown-config.test.ts
• Scenario the test should lock in: Verify that chunkFileNames correctly routes pure plugin chunks to their respective extensions/<id>/ directories, while keeping mixed/core chunks in the root.
• Why this is the smallest reliable guardrail: It directly asserts the bundler's output path logic without needing a full e2e build.
• Existing test that already covers this (if any): None
• If no new test is added, why not: N/A

User-visible / Behavior Changes

None. Plugins will now load successfully without requiring manual symlink workarounds.

Diagram (if applicable)

Before:
[extensions/slack/src/api.ts] + [extensions/slack/src/token.ts] -> dist/runtime-api-HASH.js (Fails to find node_modules)

After:
[extensions/slack/src/api.ts] + [extensions/slack/src/token.ts] -> dist/extensions/slack/shared-api-HASH.js (Successfully finds node_modules)

Security Impact (required)

• New permissions/capabilities? No
• Secrets/tokens handling changed? No
• New/changed network calls? No
• Command/tool execution surface changed? No
• Data access scope changed? No
• If any Yes, explain risk + mitigation: N/A

Repro + Verification

Environment

• OS: All
• Runtime/container: Node.js 22+
• Model/provider: N/A
• Integration/channel (if any): Slack (and any other bundled plugin with dependencies)
• Relevant config (redacted): N/A

Steps

1. Build the project using pnpm build
2. Inspect the dist/ directory and observe that Slack's shared chunks are hoisted to the root.
3. Attempt to run the gateway with the Slack plugin enabled.

Expected

The gateway starts successfully and the Slack plugin loads its dependencies from dist/extensions/slack/node_modules/.

Actual

The gateway crashes with Error: Cannot find module '@slack/web-api'.

Evidence

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

• Verified scenarios: Ran the build script and verified the output paths of the generated chunks. Added unit tests to tsdown-config.test.ts to lock in the behavior.
• Edge cases checked: Verified that core chunks and simulated cross-plugin violation chunks still fallback to the root directory.
• What you did not verify: Full E2E runtime with a live Slack workspace.

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

Compatibility / Migration

• Backward compatible? Yes
• Config/env changes? No
• Migration needed? No
• If yes, exact upgrade steps: N/A

Risks and Mitigations

• Risk: The path calculation logic might fail on certain edge-case file paths or operating systems.
  • Mitigation: Used Node's native path.resolve, path.relative, and path.sep to ensure cross-platform compatibility and immunity to parent directory naming conflicts.

Changed files

• src/infra/tsdown-config.test.ts (modified, +116/-0)
• tsdown.config.ts (modified, +38/-0)