Daniel Roe
Daniel Roe
This is intentional behaviour. Could you explain your use case for rerunning the async function on navigation?
Would you have the same feeling about ssrRefs more generally, or just with useAsync?
`useAsync` is meant to return a value. If no value is returned it will run it again.
@aldarund You _can_ use it to do that: https://stackblitz.com/edit/github-s9qt7x?file=pages%2Findex.vue. But if you don't want it to be run more than once you will need to ensure a value - any...
Yes, this is an unavoidable consequence of the Nuxt 2 fetch implementation (which entails stringifying the entire component state). I'd recommend avoiding `useFetch` and using `useAsync` instead for more granular...
You should not manipulate the store within `useFetch`. Instead use `useAsync`, which does not stringify the entire component state.
No, it will not.
Would you provide a reproduction please? 🙏
@TrungRueta Would you provide a reproduction via https://template.nuxtjs.org ? 🙏
Would you provide a reproduction please?