mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Tyler Slaton
7673b8dfb8
CI build runners use a Node with native TypeScript stripping enabled (process.features.typescript), so tsdown selects its native ESM config loader. That loader cannot resolve the extensionless relative import "../../scripts/tsdown-exports" in each tsdown.config.ts, so every package build failed with "Cannot find module" — cascading into the unit, runtime, and all integration jobs (which run the build first). Local builds used tsdown's bundler loader instead, which is why this passed pre-push. Ship the shared helper as scripts/tsdown-exports.mjs (real ESM) plus a hand-written tsdown-exports.d.mts, imported with the explicit .mjs extension. This resolves under the native loader, tsdown's bundler loader, and tsc alike. The generated exports are unchanged — package.json maps stay identical. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@copilotkit/web-inspector
Standalone Thread Inspector QA
Run the shared inspector without an app shell:
pnpm nx run @copilotkit/web-inspector:dev:standalone
Open http://127.0.0.1:5177/.
Validation steps:
- Confirm the initial
AG-UI eventsscenario opens on the Timeline tab and renders run, message, and tool rows. - Click
Messages onlyand confirm the first-visible Timeline renders persisted message content instead of an empty Timeline. - Click
Raw event onlyand confirm the Timeline renders aTHREAD_STATE_WRITTENrow with a source-event link. - Use a Timeline source-event link and confirm it opens the Raw AG-UI Events tab on the corresponding event.
- Open the State tab and confirm the demo state is visible.
This harness uses demo provider data only. Manual product validation for Intelligence-backed threads still needs a real Intelligence backend.