Repository navigation
Declaration-build failures surface as catch-all AB5000 with the TypeScript diagnostics swallowed #176
Description
Problem
Today an emit-only TS4023 regression—exported factories referencing an unexported type (#150 / #174)—surfaced only as:
error Failed to generate declaration files. (agent-bundle-index)
[{"code":"AB5000","message":"Error occurred in agent-bundle-index declaration files generation."}]
The five underlying TS4023 diagnostics were hidden by rslib's one-line error.
This creates two DX problems:
- It conflates declaration-build failures with AB5000's dev-lock meaning ("another dev process owns this project"), which misled initial triage.
- It forced a manual
tsc --declaration --emitDeclarationOnlyreplay to reveal the actual errors.
Requested improvements
- Surface the underlying TypeScript diagnostics—including file, line, and diagnostic code—through the declaration-build failure path.
- Give declaration-build failures their own AB code instead of using the AB5000 catch-all.
- Add a hint that emit-only errors can be invisible to
--noEmit.
See #174's root-cause writeup for the concrete regression and diagnosis.
Activity
ScriptedAlchemy commentedon Sep 2, 2026
Delivered in #265 (merge cee25b8).
libfamily) — never the AB5000 catch-all whose dev-lock meaning misled the feat(routes): migrate audiobook curator to public authoring #150/fix(examples): export CliCommandDefinition so declaration emit can name it #174 triage.typescript, and emits one AB4716 error per recovered diagnostic with file,(line,column), TS code, and compiler message (plussourcePath), in both human and--jsonoutput.tsc --noEmit; reproduce withtsc --declaration --emitDeclarationOnly.typescript, or the replay passes), the failure still reports as a single AB4716 with the bundler's message.docs/diagnostics.md; covered by an integration test reproducing the feat(routes): migrate audiobook curator to public authoring #150-shape TS4023 fixture end-to-end through the CLI.Known limitation (noted in the PR): detection keys on rsbuild-plugin-dts's prose failure line since it exposes no structured signal; a reworded upstream message degrades to the old catch-all rather than breaking.