feat(#2160): support @tanstack/vue-query

[hirotaka]

Changes

Implements https://github.com/openapi-ts/openapi-typescript/issues/2160.

How to Review

How can a reviewer review your changes? What should be kept in mind for this review?

Checklist

• [x] Unit tests updated
• [x] docs/ updated (if necessary)
• [x] pnpm run update:examples run (only applicable for openapi-typescript)

[netlify[bot]]

❌ Deploy Preview for openapi-ts failed.

Name	Link
🔨 Latest commit	885f06b605dd2e3a91ecbab87481f2ff1158d281
🔍 Latest deploy log	https://app.netlify.com/projects/openapi-ts/deploys/67b4683a4f081400088b2ef6

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: ed1a7e6713c485a9a6780243739ea2be172f6e10

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[drwpow]

@hirotaka thanks so much for your proposal, and for doing all the work! Unfortunately we can’t accept this PR because of some shifts in ownership structure (it’s not you, it’s us!).

Over the past several months we’ve been shifting the project into less me-led (the original creator), and more community-led through governance and shared ownership. We’ve had some discussions about project direction more specifically last few weeks, and have come to the conclusion that we can’t maintain all the ecosystem wrappers for openapi-fetch. In fact, in the future, we may even have to deprecate the openapi-react-query/swr-openapi wrappers. The only thing we know is we can’t take on additional packages.

This actually conflicts with things we’ve said we’d accept in the past, so this is a shift which is on us! But we’re trying to offshed maintenance so that the core can be stronger, and we can go deeper on a few things rather than going too shallow/too little on too many things.

---

So all that to say, I would love to help set you up to publish/own this yourself! Feel free to “steal” any infrastructure or setup here (it’s MIT licensed!), and please tag me on your own repo and I would be happy to help you publish/maintain this yourself. I would love for this to exist, especially since you did all the work! Just at this time we don’t have the resources to maintain it, and we would hamper its development.

Please let me know how I can help you push this forward outside of this repo though!