Files
sdk-fetch/tsconfig.esm.json
zeekay 120bddb520 the Hanzo API on the host's own fetch, with nothing installed beside it
A projection of hanzoai/cloud's openapi.yaml at the ref .spec-lock names —
2479 operations, 192 api classes, 2460 models — generated by hanzoai/openapi's
generate.py from the `fetch` row of its sdks.yaml. Nothing under src/ is
written by hand.

It exists because axios brings 27 packages and 4.1 MB where this brings none,
and because `…Raw()` hands back the Response, so a stream is readable. Relative
imports carry .js, so the ESM half loads in Node, Deno and a Worker rather than
only in a bundler — hanzo.yml gates that by importing the built client, which
is the one failure tsc cannot see.
2026-08-14 21:13:40 -07:00

14 lines
487 B
JSON

{
"extends": "./tsconfig.json",
"compilerOptions": {
"module": "ESNext",
// The generated client writes `./runtime.js` on every relative import —
// the sdks.yaml row asks the generator for the extension — so this half is
// loadable by Node's ESM loader and not only by a bundler. It is what
// `exports.import` points at, beside a `dist/esm/package.json` the build
// writes to mark it.
"moduleResolution": "Bundler",
"outDir": "dist/esm"
}
}