Recent challenges with this package.

[DanielRivers]

Last run update on the 9th July using @hey-api/openapi-ts@0.48.2, wanting to update my package today run into some issues.

1. can no longer run using npx @hey-api/openapi-ts due to the requirement of the separate client package to be installed, I can install but running via npx which I have been for months
2. The input structure has changed significantly. While I understand the change its difficult to manage as the versions are not semver, each update is little eggshell as not sure if its breaking change or not. This change is quite impactful, is there a way to revert to the older mechanism so I can manage the breaking change myself better?

I tried to locate the PR which made this change, but was unable to do so

[mrlubos]

Hey @DanielRivers, you'll want to read the migration notes, should be fairly straightforward https://heyapi.vercel.app/openapi-ts/migrating.html#v0-51-0

If you do decide to use the new clients, yes, that's a huge changeset, which is why they've been released completely separate. There probably should be a migration helper at some point, but the effort is not worth it right now

[DanielRivers]

I am wondering if I could possibly expose the legacy fetch and the new fetch module as with different import paths in my package. This something which could be done natively or would I have to run the script multiple times?

[mrlubos]

I am wondering if I could possibly expose the legacy fetch and the new fetch module as with different import paths in my package. This something which could be done natively or would I have to run the script multiple times?

Why would you want to do that?

[mrlubos]

Whats the future look like for client: fetch? will that be deprecated ?

I think it would make sense for v1, but there's no rush to do that right now

[DanielRivers]

I am wondering if I could possibly expose the legacy fetch and the new fetch module as with different import paths in my package. This something which could be done natively or would I have to run the script multiple times?

Why would you want to do that?

We offer the generated code as an external tool for customers. As the new module is a breaking change we want to offer a transition option so supplying both for a period of time to save us maintaining two versions.

[mrlubos]

Do you have any suggestions what that would look like from the user/API perspective?