Tyler Slaton 7673b8dfb8 fix(build): load tsdown exports helper as .mjs under native config loader ...

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>

2026-07-09 20:39:07 -07:00

..

src

fix: repair check-types across all packages and gate it in CI

2026-06-23 15:26:47 -07:00

CHANGELOG.md

chore: version packages

2026-04-10 23:38:59 +00:00

package.json

fix(build): add types condition to package.json exports maps (#3324)

2026-07-09 20:38:10 -07:00

tsconfig.json

refactor: consolidate V1/V2 packages into flat @copilotkit/* structure

2026-03-28 16:45:10 -07:00

tsdown.config.ts

fix(build): load tsdown exports helper as .mjs under native config loader

2026-07-09 20:39:07 -07:00

vitest.config.mjs

chore(runtime): update package config, CI workflows, and docs

2026-04-03 18:41:27 +02:00