Nuxt 4 - useFetch breaks when using the "default" option

I have a component that calls useFetch.

const { data, pending, error } = await useFetch(`/api/${props.apiEndpoint}`, {
  method: 'POST',
  body,
  key: hash(`${props.apiEndpoint}-${props.apiKey}-${today}`),
  default () {
    return {
      budget: 0,
      actual: 0,
      difference: 0,
    }
  },
})

const { data, pending, error } = await useFetch(`/api/${props.apiEndpoint}`, {
  method: 'POST',
  body,
  key: hash(`${props.apiEndpoint}-${props.apiKey}-${today}`),
  default () {
    return {
      budget: 0,
      actual: 0,
      difference: 0,
    }
  },
})

This component is only rendered on the client. I boot this component up twice with different endpoints. When the default parameter is specified no network call is made. I've ensured that the key is unique for each component. If I remove the default parameter things work fine. I feel like this is a bug.

Nuxt•7mo ago•

5 replies

Byte

Nuxt 4 - useFetch breaks when using the "default" option

I have a component that calls useFetch.

const { data, pending, error } = await useFetch(`/api/${props.apiEndpoint}`, {
  method: 'POST',
  body,
  key: hash(`${props.apiEndpoint}-${props.apiKey}-${today}`),
  default () {
    return {
      budget: 0,
      actual: 0,
      difference: 0,
    }
  },
})

const { data, pending, error } = await useFetch(`/api/${props.apiEndpoint}`, {
  method: 'POST',
  body,
  key: hash(`${props.apiEndpoint}-${props.apiKey}-${today}`),
  default () {
    return {
      budget: 0,
      actual: 0,
      difference: 0,
    }
  },
})

Nuxt 4 - useFetch breaks when using the "default" option

Similar Threads

Nuxt 4 - useFetch breaks when using the "default" option

Similar Threads

Similar Threads

Similar Threads