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 - Runtime Client GQL
✨ Why CopilotKit?
- Minutes to integrate - Get started quickly with our CLI
- Framework agnostic - Works with React, Next.js, AGUI and more
- Production-ready UI - Use customizable components or build with headless UI
- Built-in security - Prompt injection protection
- Open source - Full transparency and community-driven
🧑💻 Real life use cases
Deploy deeply-integrated AI assistants & agents that work alongside your users inside your applications.
🏆 Featured Examples
Documentation
To get started with CopilotKit, please check out the documentation.