Interface: BundlerInspectionEntry
agent-bundle inspect --bundler (RFC #50 §3.4): surfaces the internal
Rslib/Rsbuild configurations the build composes — the framework profile
with the consumer tools escape hatch merged over it and the invariant
hook appended last — for every synthesized output. The composition comes
from the same functions the build lowers (composeEntryLibConfig,
composeMcpAppsRsbuildConfig), so the inspection can never drift from
what actually compiles.
Two build-time-only values are replaced with stable tokens so the output
is deterministic for one project: the artifact output root (chosen by
build --output and staged per build) appears as <output>/<target>,
and the synthesized declaration tsconfig (a temporary file the package
build generates under node_modules) appears as
<generated-dts-tsconfig>. Nothing else is redacted; this is a local
debugging surface.
Properties
bundler
readonlybundler:"rsbuild"|"rslib"
config
readonlyconfig:unknown
The composed config, JSON-rendered: functions appear as [function <name>].
generatedEntry?
readonlyoptionalgeneratedEntry?:string
The generated wrapper entry module, when the framework provides one.
kind
readonlykind:"hook"|"script"|"bin"|"lib"|"mcp-apps"|"mcp-entry"
name
readonlyname:string
outputPath
readonlyoutputPath:string
POSIX output path relative to the artifact root (targets) or project root (package build).
source?
readonlyoptionalsource?:string
The authored entry module (absent for the per-target MCP Apps config).
target?
readonlyoptionaltarget?:string