Watch retries and throttling as they happen

Task

A call is slow or flaky and you want to see why — the retry that fired, the throttle that paused, the field that drifted — not just the final value or a thrown error.

Example

One way: iterate the stitch's event stream instead of awaiting it.

import { stitch } from 'stitchapi';

const search = stitch({ baseUrl: 'https://api.example.com', path: '/search' });

// Await for just the value…
const value = await search({ query: { q: 'mango' } });

// …or iterate the stream for everything that happened on the way there.
for await (const event of search({ query: { q: 'mango' } }).stream()) {
    if (event.type === 'progress') console.log(event.phase, event.attempt);
    if (event.type === 'drift')
        console.log(event.finding.level, event.finding.path);
    if (event.type === 'result') console.log(event.data);
}

How it works

A stitch yields a typed event stream — start → progress → drift → result → done — and await simply consumes it for the final value. .stream() hands you the events instead, discriminated on type, so narrowing one field tells the compiler the shape of the rest. progress carries a phase (auth, throttled, retry, pagination, circuit) and an attempt; drift carries leveled findings — including the warn/info ones that never throw; then exactly one terminal result or error, then done. This is the one source every cross-cutting feature reports through, and exactly what a trace sink consumes.

See also