Nuxt data fetching (useFetch, useAsyncData) in Vue - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is useFetch in Nuxt?

useFetch is a composable in Nuxt that helps you fetch data easily in your components. It automatically handles loading, error states, and caching.

intermediate

How does useAsyncData differ from useFetch?

useAsyncData is similar to useFetch but is more flexible. It lets you fetch any async data, not just HTTP requests, and is often used for server-side data fetching.

beginner

What does useFetch return?

useFetch returns an object with data, pending, and error properties to track the fetched data, loading state, and errors.

intermediate

When should you use useAsyncData in Nuxt?

Use useAsyncData when you want to fetch data on the server side before the page renders, or when you need more control over the async operation beyond HTTP requests.

intermediate

How do useFetch and useAsyncData help with SEO in Nuxt?

Both fetch data before the page renders, so the HTML sent to the browser already has the data. This helps search engines see the full content, improving SEO.

Which Nuxt composable automatically tracks loading and error states when fetching data?

A useFetch

B useState

C useRouter

D useHead

useFetch automatically tracks loading and error states when fetching data.

What is a key difference between useFetch and useAsyncData?

A <code>useFetch</code> is only for server-side data

B <code>useAsyncData</code> can fetch any async data, not just HTTP requests

C <code>useAsyncData</code> does not support error handling

D <code>useFetch</code> returns a promise

useAsyncData is more flexible and can fetch any async data, not just HTTP requests.

Which property from useFetch tells you if data is still loading?

A data

B result

C error

D pending

The pending property is true while data is loading.

Why is fetching data before page render important for SEO in Nuxt?

A It sends full content in HTML for search engines to read

B It hides data from search engines

C It disables JavaScript

D It makes pages load slower

Fetching data before render sends full content in HTML, helping search engines index the page better.

Which Nuxt composable would you use to fetch data on the server before the page loads?

A useState

B useFetch

C useAsyncData

D useRouter

useAsyncData is designed for server-side data fetching before page render.

Explain how useFetch works in Nuxt and what it returns.

Think about what you get when you call useFetch in a component.

Describe when and why you would use useAsyncData instead of useFetch in Nuxt.

Consider server rendering and types of async tasks.

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