Nuxt data fetching (useFetch, useAsyncData) in Vue

Introduction

We use useFetch and useAsyncData in Nuxt to get data from servers easily. They help show data on pages while keeping things fast and smooth.

When you want to load data from an API to show on a page.

When you need to get data before the page appears to the user.

When you want to fetch data that updates automatically when the page changes.

When you want to handle loading and error states simply.

When you want to share fetched data between server and client without extra work.

Syntax

Vue

const { data, pending, error } = useFetch(url, options)

const { data, pending, error } = useAsyncData(key, fetcherFunction, options)

useFetch is a shortcut to fetch data from a URL directly.

useAsyncData lets you use any async function to get data, with a unique key to cache it.

Examples

Fetches user data from the API URL directly.

Vue

const { data, pending, error } = useFetch('https://api.example.com/users')

Fetches user data using a function and caches it with the key 'users'.

Vue

const { data, pending, error } = useAsyncData('users', () => $fetch('https://api.example.com/users'))

Fetches posts with a POST request instead of GET.

Vue

const { data, pending, error } = useFetch('https://api.example.com/posts', { method: 'POST' })

Sample Program

This component fetches a list of users from a public API. It shows a loading message while waiting, an error message if something goes wrong, and the user list when data is ready. It uses semantic HTML and ARIA for accessibility.

Vue

<script setup>
const { data: users, pending, error } = useFetch('https://jsonplaceholder.typicode.com/users')
</script>

<template>
  <section aria-live="polite">
    <h1>Users List</h1>
    <div v-if="pending">Loading users...</div>
    <div v-else-if="error">Error loading users.</div>
    <ul v-else>
      <li v-for="user in users" :key="user.id">
        <strong>{{ user.name }}</strong> - {{ user.email }}
      </li>
    </ul>
  </section>
</template>

Important Notes

Both useFetch and useAsyncData run on server and client automatically.

Use the pending property to show loading states for better user experience.

Always handle error to show friendly messages if data fails to load.

Summary

useFetch is a quick way to get data from a URL.

useAsyncData is more flexible and uses a key to cache data.

Both help load data before showing the page, improving speed and user experience.

Practice

1. What is the main difference between useFetch and useAsyncData in Nuxt?

easy

A. useAsyncData automatically refreshes data, useFetch never does.

B. useAsyncData requires a unique key for caching, useFetch does not.

C. useFetch is only for server-side, useAsyncData is client-side only.

D. useFetch caches data with a key, useAsyncData fetches without caching.

Solution

1. Step 1: Understand useFetch behavior

   useFetch fetches data from a URL quickly but does not require a key for caching.

2. Step 2: Understand useAsyncData behavior

   useAsyncData needs a unique key to cache the fetched data, allowing more control over data reuse.

3. Final Answer:

   useAsyncData requires a unique key for caching, useFetch does not. -> Option B

4. Quick Check:

   Key caching difference = D [OK]

Hint: Remember: useAsyncData needs a key, useFetch is simpler [OK]

Common Mistakes:

• Thinking useFetch caches data with keys
• Confusing client/server usage of both
• Assuming useAsyncData auto-refreshes data

2. Which of the following is the correct syntax to use useAsyncData in a Nuxt component?

easy

A. const { data } = useAsyncData('posts', () => $fetch('/api/posts'))

B. const data = useAsyncData('/api/posts')

C. useAsyncData(() => $fetch('posts'), 'posts')

D. const { data } = useAsyncData(() => fetch('/api/posts'))

Solution

1. Step 1: Check the required parameters for useAsyncData

   The first parameter is a unique key string, the second is a function returning a promise.

2. Step 2: Validate each option's syntax

   const { data } = useAsyncData('posts', () => $fetch('/api/posts')) correctly uses a key 'posts' and a fetch function with $fetch. Others miss the key or use wrong order.

3. Final Answer:

   const { data } = useAsyncData('posts', () => $fetch('/api/posts')) -> Option A

4. Quick Check:

   Key first, fetch function second = A [OK]

Hint: Key string first, fetch function second in useAsyncData [OK]

Common Mistakes:

• Omitting the key parameter
• Swapping parameters order
• Using native fetch instead of $fetch

3. Given this code snippet in a Nuxt component:

const { data, pending } = useFetch('/api/user')

return { data, pending }

What will pending be initially when the component loads?

medium

A. undefined

B. false

C. true

D. null

Solution

1. Step 1: Understand useFetch loading state

   pending is a reactive boolean indicating if the fetch is still in progress.

2. Step 2: Initial value of pending

   When the component loads and fetch starts, pending is true until data arrives.

3. Final Answer:

   true -> Option C

4. Quick Check:

   Loading state pending = true [OK]

Hint: pending is true while fetching data [OK]

Common Mistakes:

• Assuming pending is false initially
• Confusing pending with data presence
• Expecting pending to be null or undefined

4. You wrote this code in a Nuxt component:

const { data } = useAsyncData(() => $fetch('/api/items'))

But the data never loads. What is the likely problem?

medium

A. Using $fetch instead of native fetch.

B. Returning data directly instead of inside a function.

C. Not awaiting the useAsyncData call.

D. Missing a unique key as the first argument to useAsyncData.

Solution

1. Step 1: Check useAsyncData parameters

   useAsyncData requires a unique key string as the first argument for caching.

2. Step 2: Identify missing key issue

   Omitting the key causes the fetch not to run properly or cache data, so data never loads.

3. Final Answer:

   Missing a unique key as the first argument to useAsyncData. -> Option D

4. Quick Check:

   Key missing in useAsyncData = B [OK]

Hint: Always provide a key string first in useAsyncData [OK]

Common Mistakes:

• Skipping the key argument
• Confusing $fetch with fetch as cause
• Expecting useAsyncData to be awaited

5. You want to fetch user data and posts in a Nuxt page using useAsyncData. You want posts to refresh every time the user ID changes. Which approach correctly achieves this?

hard

A. Use useAsyncData with a key including the user ID, e.g., useAsyncData(`posts-${userId}`, () => $fetch(`/api/posts?user=${userId}`)).

B. Use useAsyncData with a fixed key 'posts' and rely on automatic refresh.

C. Use useFetch instead of useAsyncData because it auto-refreshes on param change.

D. Call useAsyncData without a key and manually watch userId to refetch.

Solution

1. Step 1: Understand caching with keys in useAsyncData

   Keys uniquely identify cached data. Changing the key triggers a new fetch.

2. Step 2: Use dynamic key with user ID

   Including userId in the key string ensures posts refetch when userId changes.

3. Step 3: Evaluate other options

   Fixed keys won't refresh; useFetch doesn't auto-refresh on param change; manual watch is more complex.

4. Final Answer:

   Use useAsyncData with a key including the user ID, e.g., useAsyncData(`posts-${userId}`, () => $fetch(`/api/posts?user=${userId}`)). -> Option A

5. Quick Check:

   Dynamic key triggers refetch = C [OK]

Hint: Include changing params in key string for refetch [OK]

Common Mistakes:

• Using fixed keys expecting auto-refresh
• Assuming useFetch auto-refreshes on param change
• Skipping key causes no caching or refetch