Nuxt 3 VS ofetch

- https://github.com/nuxt/framework: An intuitive framework for building web applications, built for the edge.

It uses Nuxi for Command line interface,

Note, the repo linked below, https://github.com/danielroe/nuxt-zero-js, was an experiment that I subsequently moved into Nuxt core: https://github.com/nuxt/framework/pull/7248. I plan to update it to test out per-route zero-JS via a route rule.

I asked this before on the Github discussion https://github.com/nuxt/framework/discussions/10073, but I haven't found an answer yet.

Also one I've reported a long time ago, that's still an issue today: If you start the Nuxt dev server without create the server/ folder, Nuxt isn't going to be able to read any of your server/api files. You have to create the folder and restart the dev server. Only then, it will start detecting your server files. This is an issue on both Windows and Linux.

Perhaps this thread can help you.

But there is a catch, nuxt.config does not allow functions in it. And it could be bother to mention this in every single page. Also, the later part is supposed to act like a Default or Fallback. Hmm.. Now what? Well, that where plugins system comes in. I can create a Plugin named title and add this logic there, which will be implemented on every page. Also, Nuxt devs mentioned this approach here.

I've found a matching issue with a solution I can use as a hotfix for now: https://github.com/nuxt/framework/issues/6648

https://github.com/nuxt/framework/issues/3587 (upstream Vue bug maybe?) https://github.com/nuxt/framework/issues/8634 https://github.com/nuxt/framework/issues/8611

This issue is where I started, and I noticed that in my project, setting the cookie header manually, or through a composable on the server-side doesn't actually set it in the browser (it doesn't show up in the developer tools). They've listed workarounds, but they're just that - the first link (when it comes back up, will show a messy composable you can write). Everything works fine with `axios` (instead of their built-in data fetching APIs), but the request seems to be executed twice on page load for some reason.

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: