ofetch VS axios

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:

axios

Also, copy this code to add axios

Typically, there are various ways to choose an HTTP client, and for this example, I've chosen axios.

axios: To fetch data from the Strapi CMS API and also to fetch responses from our Express server.

Note, you can use any library for HTTP requests like axios. This example uses the http and node-fetch libraries available on npm.

Interact with other APIs over an encrypted channel. For example, you can use Axios with Node.js.

For this article, I will be using the TypeScript Starter template as shown in the screenshot above. This comes with Nodejs, Cheerio, Axios

Axios is suitable for a wide range of web development projects, from simple single-page applications (SPAs) to complex, large-scale enterprise software.

Axios for streamlined API interactions, facilitating seamless data fetching.

Axios is a popular HTTP client library for Node.js that provides a more user-friendly and feature-rich way to make HTTP requests. Axios simplifies error handling and supports features like automatic JSON parsing and request/response interceptors, making it a great choice for many HTTP request scenarios.