Closed
Description
The way we call the generator from another repo is embarrassingly bad, which is ok if we're only using it in one repo, but if we want to use this to generate TS clients for other APIs, and we want people to be able to regen their clients easily on API changes, this needs improvement. Ideally you'd be able to do something like
npx @oxide/ts-openapi-gen my-schema.json output-dir/
One possibly easy path to that is through JSR, and this would be a good low-stakes way to experiment. They don't yet support a bin
field in the package.json
they generate for npm
(which is what powers npx
), but they have a PR for it that is being actively worked on.
Metadata
Metadata
Assignees
Labels
No labels