idea: use createUseFetch for generated composables on newer Nuxt

[onmax]

Nuxt now has createUseFetch (nuxt@>=4.4.0) for custom useFetch instances, and the recommended custom useFetch recipe seems to be moving in that direction.

Would you be open to nuxt-open-fetch adopting that for generated use[Client] / useLazy[Client] composables when the installed Nuxt version supports it, while keeping the current createUseOpenFetch path for older Nuxt versions?

My thought is to keep it small:

• do the split at generation time, not at runtime
• keep the public generated API unchanged
• only use the new path when the feature is available in Nuxt

Resources:

• custom useFetch recipe: https://nuxt.com/docs/guide/recipes/custom-usefetch#custom-usefetchuseasyncdata
• Nuxt 4.4 release notes (createUseFetch section): https://github.com/nuxt/nuxt/releases/tag/v4.4.0#createusefetch-and-createuseasyncdata

If that direction makes sense, I can put together a PR.

Reasons why i think make sesne

• it aligns nuxt-open-fetch with Nuxt’s current recommended custom useFetch direction
• it should reduce maintenance / compatibility risk in future
• no public api change

[Norbiros]

I agree, that would clean up a lot of code in this project.