You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
On second thought, it sounds like JSR’s npm compatibility mode requires extra setup on the caller side to get npm to use the JSR registry. If that’s right, then this makes no sense as a thing to do. Just use npm directly the normal way.
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
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 thepackage.json
they generate fornpm
(which is what powersnpx
), but they have a PR for it that is being actively worked on.The text was updated successfully, but these errors were encountered: