Similar issues - #27439 - nuxt/nuxt - unsight.dev

# use server-fetched data in lazily hydrated components with useAsyncData

use server-fetched data in lazily hydrated components with useAsyncData

nuxt/nuxt · updated7 months ago · 38% similar

good first issue🍰 p2-nice-to-have

useFetch returns null used in component when on parent data is loaded via composable useFetch on route watch

nuxt/nuxt · updated1 year ago · 34% similar

pending triage

useAsyncData doesn't reuse ssr payload on client side

nuxt/nuxt · closed3 years ago · 39% similar

3.xpending triage

useAsyncData returns undefined in SSR when component is used multiple times

nuxt/nuxt · closed2 months ago · 38% similar

pending triage

api call handling different between ssr and client with useFetch and useAsyncData

nuxt/nuxt · closed7 months ago · 36% similar

pending triage

`useOnce` composable: execute data fetching function only once either on server or client

nuxt/nuxt · closed9 months ago · 36% similar

pending triage

API requests are called twice in lazy hydrated components that use useFetch / useAsyncData

nuxt/nuxt · closed3 months ago · 35% similar

pending triage

useAsyncData doesn't update ssrContext on page refresh

nuxt/nuxt · closed1 year ago · 35% similar

pending triagenitroneeds reproductionclosed-by-bot

Responses from two components using useAsyncData with different Props values are identical

nuxt/nuxt · closed2 years ago · 35% similar

3.xpending triage

useAsyncData is running twice refetching data (server and client)

nuxt/nuxt · closed2 years ago · 35% similar

3.xpending triage