useAsyncData
useAsyncData provides access to data that resolves asynchronously in an SSR-friendly composable.
Within your pages, components, and plugins you can use useAsyncData to get access to data that resolves asynchronously.
useAsyncData is a composable meant to be called directly in the Nuxt context. It returns reactive composables and handles adding responses to the Nuxt payload so they can be passed from server to client without re-fetching the data on client side when the page hydrates.Usage
pages/index.vue
<script setup lang="ts">
const { data, status, error, refresh, clear } = await useAsyncData(
'mountains',
() => $fetch('https://api.nuxtjs.dev/mountains')
)
</script>
If you're using a custom useAsyncData wrapper, do not await it in the composable, as that can cause unexpected behavior. Please follow this recipe for more information on how to make a custom async data fetcher.
data, status and error are Vue refs and they should be accessed with .value when used within the <script setup>, while refresh/execute and clear are plain functions.Watch Params
The built-in watch option allows automatically rerunning the fetcher function when any changes are detected.
pages/index.vue
<script setup lang="ts">
const page = ref(1)
const { data: posts } = await useAsyncData(
'posts',
() => $fetch('https://fakeApi.com/posts', {
params: {
page: page.value
}
}), {
watch: [page]
}
)
</script>
useAsyncData is a reserved function name transformed by the compiler, so you should not name your own function useAsyncData .Params
key: a unique key to ensure that data fetching can be properly de-duplicated across requests. If you do not provide a key, then a key that is unique to the file name and line number of the instance ofuseAsyncDatawill be generated for you.handler: an asynchronous function that must return a truthy value (for example, it should not beundefinedornull) or the request may be duplicated on the client side.Thehandlerfunction should be side-effect free to ensure predictable behavior during SSR and CSR hydration. If you need to trigger side effects, use thecallOnceutility to do so.options:server: whether to fetch the data on the server (defaults totrue)lazy: whether to resolve the async function after loading the route, instead of blocking client-side navigation (defaults tofalse)immediate: when set tofalse, will prevent the request from firing immediately. (defaults totrue)default: a factory function to set the default value of thedata, before the async function resolves - useful with thelazy: trueorimmediate: falseoptiontransform: a function that can be used to alterhandlerfunction result after resolvinggetCachedData: Provide a function which returns cached data. Anullorundefinedreturn value will trigger a fetch. By default, this is:Which only caches data whenconst getDefaultCachedData = (key, nuxtApp) => nuxtApp.isHydrating ? nuxtApp.payload.data[key] : nuxtApp.static.data[key]experimental.payloadExtractionofnuxt.configis enabled.pick: only pick specified keys in this array from thehandlerfunction resultwatch: watch reactive sources to auto-refreshdeep: return data in a deep ref object (it istrueby default). It can be set tofalseto return data in a shallow ref object, which can improve performance if your data does not need to be deeply reactive.dedupe: avoid fetching same key more than once at a time (defaults tocancel). Possible options:cancel- cancels existing requests when a new one is madedefer- does not make new requests at all if there is a pending request
Under the hood,
lazy: false uses <Suspense> to block the loading of the route before the data has been fetched. Consider using lazy: true and implementing a loading state instead for a snappier user experience.Learn how to use
transform and getCachedData to avoid superfluous calls to an API and cache data for visitors on the client.Return Values
data: the result of the asynchronous function that is passed in.refresh/execute: a function that can be used to refresh the data returned by thehandlerfunction.error: an error object if the data fetching failed.status: a string indicating the status of the data request:idle: when the request has not started, such as:- when
executehas not yet been called and{ immediate: false }is set - when rendering HTML on the server and
{ server: false }is set
- when
pending: the request is in progresssuccess: the request has completed successfullyerror: the request has failed
clear: a function which will setdatatoundefined, seterrortonull, setstatusto'idle', and mark any currently pending requests as cancelled.
By default, Nuxt waits until a refresh is finished before it can be executed again.
If you have not fetched data on the server (for example, with
server: false), then the data will not be fetched until hydration completes. This means even if you await useAsyncData on the client side, data will remain null within <script setup>.Type
Signature
function useAsyncData<DataT, DataE>(
handler: (nuxtApp?: NuxtApp) => Promise<DataT>,
options?: AsyncDataOptions<DataT>
): AsyncData<DataT, DataE>
function useAsyncData<DataT, DataE>(
key: string,
handler: (nuxtApp?: NuxtApp) => Promise<DataT>,
options?: AsyncDataOptions<DataT>
): Promise<AsyncData<DataT, DataE>>
type AsyncDataOptions<DataT> = {
server?: boolean
lazy?: boolean
immediate?: boolean
deep?: boolean
dedupe?: 'cancel' | 'defer'
default?: () => DataT | Ref<DataT> | null
transform?: (input: DataT) => DataT | Promise<DataT>
pick?: string[]
watch?: WatchSource[]
getCachedData?: (key: string, nuxtApp: NuxtApp) => DataT | undefined
}
type AsyncData<DataT, ErrorT> = {
data: Ref<DataT | null>
refresh: (opts?: AsyncDataExecuteOptions) => Promise<void>
execute: (opts?: AsyncDataExecuteOptions) => Promise<void>
clear: () => void
error: Ref<ErrorT | null>
status: Ref<AsyncDataRequestStatus>
};
interface AsyncDataExecuteOptions {
dedupe?: 'cancel' | 'defer'
}
type AsyncDataRequestStatus = 'idle' | 'pending' | 'success' | 'error'