CodeVetter · Repo Unpack · Behavior traces
unjs/ofetch
Source reading followed initialization, a JSON POST, and HTTP failure with retry through their complete call chains. Additional branches cover custom clients, streaming, and transport rejection. The same raw function owns preprocessing, fetch, decoding, hooks, and status handling. These are static execution traces rather than observed runs.
- Initialization proceeds index.ts → base.ts exports → entrypoint fetch wrapper → createFetch({ fetch }) → ofetch/$fetch aliases; unsupported global fetch uses the rejecting wrapper.
- A JSON POST proceeds $fetch → $fetchRaw → resolveFetchOptions → uppercase method → onRequest → withBase/withQuery → isJSONSerializable → JSON.stringify and default headers.
- After POST preparation, fetch runs → response type is selected → response text is parsed into _data → onResponse runs → status is checked → $fetch returns _data.
- A qualifying 408 response is decoded first → onResponse → onResponseError → onError → retry budget/status check → optional retryDelay → recursive $fetchRaw with retry decremented.
- When retry is unavailable or exhausted, onError calls createFetchError, optionally trims the V8 stack, and throws an error exposing URL, status, context, and decoded body.
- A transport rejection sets context.error → awaits onRequestError → enters onError; AbortError suppresses automatic retry only when timeout is absent.
- Client creation proceeds $fetch.create → shallow global/default merging → createFetch; later calls independently merge headers and query through resolveFetchOptions.
- An SSE response follows content-type detection → stream branch → response.body or _bodyInit assigned to _data → caller receives the stream and reads chunks itself.