[Copilot]

Multi-client packages failed to build with DIST_MISSING: the generated config/tsconfig.src.*.json files hardcoded include: ["../src/index.ts"], while warp.config.yml exported every client's entry point as a separate subpath (./devCenter → ./src/devCenter/index.ts). Since the root src/index.ts imports the deeper client/api files directly instead of re-exporting the per-client barrels, TypeScript never emitted those barrels to dist, and warp's export validation failed.

Changes

• build-ts-config.ts: New getSrcIncludePaths(exports) derives the include list from the same exports map that drives warp.config.yml — mapping ./src/... → ../src/..., dropping non-.ts values (e.g. package.json), de-duplicating, and always keeping ../src/index.ts as fallback. The four buildTsSrc{Esm,Browser,ReactNative,Cjs}Config builders now take exports.
• index.ts: Threads modularPackageInfo.exports into the buildTsSrc*Config builders in both the initial-generation and update/migration paths, keeping the tsconfig inputs and warp exports in sync.
• Tests: test-next/unit/metadata/ts-config.test.ts covering default fallback, multi-client sync, non-.ts filtering, de-duplication, and per-target propagation.

For the multi-client example in the issue, the emitted configs now include every exported barrel:

// config/tsconfig.src.esm.json
"include": [
  "../src/index.ts",
  "../src/devCenter/index.ts",
  "../src/devCenter/api/index.ts",
  "../src/devBoxes/index.ts",
  "../src/deploymentEnvironments/index.ts",
  "../src/models/index.ts"
]

[ZiWei Chen (kazrael2119)]

Copilot resolve conflicts

[Copilot]

Copilot resolve conflicts

Resolved the conflict in build-ts-config.ts (merged main in f1edda4). Kept both main's compilerOptions.resolveJsonModule and the getSrcIncludePaths(exports) include change. Build and metadata unit tests pass.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@azure-tools/typespec-ts@4872

commit: c14f9cd

[Jialin Huang (JialinHuang803)]

Overall looks good to me. Just left some suggestions to simplify the comments.

[github-actions]

All changed packages have been documented.

• ✅ @azure-tools/typespec-ts

Show changes

@azure-tools/typespec-ts - fix ✏️

Fix multi-client package build failures by syncing the generated config/tsconfig.src.*.json include lists with the warp.config.yml exports, so every client entry point is compiled and emitted to dist (previously warp failed with DIST_MISSING).

[Connor Wood (Connor-Wood)]

Could this get a patch release off release/july-2026? 008ad69c2 is main-only right now, so otherwise it waits for August.

We're blocked on it in Azure/azure-rest-api-specs#45038 - Content Safety declares 3 @client interfaces and hits this exact DIST_MISSING path (build, emitter 0.55.1). It's the only failing check, and nothing in tspconfig.yaml can work around it.

typespec-java got patches off that branch three times last week (#5046, #5019, #4958). A dev build with the fix would unblock us too.

[Jialin Huang (JialinHuang803)]

Hi Connor Wood (@Connor-Wood) we've released a hot fix for it. The JS SDK automation pipeline failure of your PR should be resolved.