ofetch VS vue-next

useFetch uses the oFetch client per the documentation

Create a similar webshits lib

and rolled my own retry/caching/timeout implementation using https://github.com/unjs/ohmyfetch interceptors

It's not entirely clear, I'd agree. It takes some time getting used to the syntax changes from Nuxt 2 > Nuxt 3. All of the above methods are all just Nuxt 3 wrappers for $fetch (https://github.com/unjs/ohmyfetch) with various degrees of flexibility/control.

As I am using Nuxt 3, I use ohmyfetch https://github.com/unjs/ohmyfetch created by the Nuxt team.

Nitro allows 'direct' calling of routes via the globally-available $fetch helper. This will make an API call to the server if run on the browser, but will simply call the relevant function if run on the server, saving an additional API call. The $fetch API uses ohmyfetch to:

⚡️ Vue 3 & Vite

The project at the moment has completed feature parity with @vue/compiler-core . Compiling to dom, ssr, sfc have not yet been implemented. You can check what has been implemented in the playground

For this to work, you will need to be using vue@^3.2.25 and above. No additional dependencies are required. Vue 3.2.25+ ships an implementation under the package @vue/reactivity-transform. It is also integrated (with its APIs re-exported) in @vue/compiler-sfc so most userland projects won't need to explicitly install it.