ofetch Interceptors (onResponseError etc..)

[AntonLugtenburg]

Hello 🙂

Does anyone know if it's possible to use interceptors like onRequestError or onResponseError with nuxt-auth-sanctum?

Currently, I see support for onRequest and onResponse via defineAppConfig, but I’d like to handle cases like connection refused / no response (e.g., when the API is offline).
Are all ofetch interceptors exposed to app.config.ts, or just those two?

Thanks in advance!

Something like this

onResponseError: async (
        app: NuxtApp,
        ctx: FetchContext,
        error: FetchError,
        logger: ConsolaInstance
      ) => {

        logger.error(`[onRequestError] (${ctx.request})`, error);

        // Connection refused, API down, etc.
        if (error.message.includes("ERR_CONNECTION_REFUSED") || error.code === "FETCH_ERROR") {
          logger.error("API seems unreachable (connection refused or offline)");
        }
      }

[manchenkoff]

Hey @AntonLugtenburg! Good question 😄 I've recently covered this one via Nuxt hook which you can subscribe to - sanctum:error. Overriding ofetch interceptors is not the best way since it might conflict with an existing behaviour, so it would be better to keep your business logic separated.

[AntonLugtenburg]

But is sactum:error triggered if ERR_CONNECTION_REFUSED or the absence of a response ?

[manchenkoff]

It is triggered exactly as you wanted, inside of onResponseError interceptor, check this out for more details

[AntonLugtenburg]

i think my issue is that Fetch or ofetch does not trigger onResponseError in case of a network failure etc... it triggers onRequestError and that is not triggering the error hook in your factory

[manchenkoff]

oh, I see. Then it is a candidate for a new hook, please track it here - #350 . However, in your particular case you can just pass it as this:

const sanctumClient = useSanctumClient()

const {} = await sanctumClient('/api/endpoint', {
  async onRequestError({ request, options, error }) {
    console.log("[fetch request error]", request, error);
  },
})

Since nuxt-auth-sanctum doesn't use this interceptor, it will not interfere with anything.

[manchenkoff]

UPDATE

A new hook sanctum:error:request is available since version 0.6.4.