[cowboyd]

Motivation

Some route graphs cannot be known when parsing begins. A program may need the caller to load configuration or plugins before additional options and routes can be defined.

Configliere should support those requirements without performing I/O, introducing asynchrony, or sacrificing exact route and model types. Parsing must be able to pause, hand a typed requirement to the caller, and resume the same invocation after the caller supplies a result.

Approach

Represent a route as an ordered, non-empty sequence of phases. A phase owns the parameters and child routes available at that point; once it has completed, neither can retroactively consume input. A dynamic boundary attaches a typed requirement to the current phase and begins a fresh continuation phase.

Reaching that boundary yields a successful parse increment rather than an incomplete intent. The caller performs whatever external work is required and resumes with Result<Requirement>. Success applies a route extension and continues the same parse; failure enters the ordinary unprocessable-content path. Configliere therefore coordinates incremental parsing without owning I/O or introducing asynchrony.

Dynamic extensions use the same composition algebra as static definitions. They operate from an isolated continuation seed that preserves aggregate route identity and model information while recording only newly introduced phases. This makes phase chains composable without duplicating their history.

Because later phases may reveal new routes, route discovery and phase binding proceed incrementally over the original token stream. Unknown input is not rejected until the relevant route is final, but completed phases remain immutable and selected child routes establish hard ownership boundaries. Help and version obey the same process: they become intents only after every phase needed to identify their target route has resolved.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/configliere@22

commit: 2af8a67