Nuxt data fetching (useFetch, useAsyncData) in Vue - Step-by-Step Execution

Concept Flow - Nuxt data fetching (useFetch, useAsyncData)

Component Setup

↓

Call useFetch or useAsyncData

↓

Start Data Fetching

↓

Wait for Promise

↓

Success

→Store Data in Reactive State

↓

Component Renders with Data

↓

Error

→Store Error State

↓

Component Renders with Error

The component calls useFetch or useAsyncData to start fetching data asynchronously, waits for the result, then stores the data or error in reactive state for rendering.

Execution Sample

Vue

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

This code fetches data from '/api/items' and tracks loading and error states.

Execution Table

Step	Action	State Before	Result	State After	Component Render
1	Component setup starts	data: undefined, pending: undefined, error: undefined	Call useFetch	pending: true, data: undefined, error: undefined	Render loading state (pending true)
2	Fetch promise starts	pending: true	Fetching data from /api/items	pending: true	Still loading
3	Fetch promise resolves	pending: true	Data received: [{id:1,name:'A'},{id:2,name:'B'}]	pending: false, data: [{id:1,name:'A'},{id:2,name:'B'}], error: null	Render data list
4	User sees data rendered	data present	Display list items	No state change	Data visible on screen
5	If fetch failed	pending: true	Error received	pending: false, error: Error object, data: null	Render error message
6	Component unmounts	Any state	Cleanup	State cleared	Component removed
Exit	No more updates	Final state stable	No action	Stable state	Component shows final UI

💡 Data fetch completes successfully or with error, component renders accordingly and stops updating.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 5	Final
data	undefined	undefined	[{id:1,name:'A'},{id:2,name:'B'}]	null	[{id:1,name:'A'},{id:2,name:'B'}] or null
pending	undefined	true	false	false	false
error	undefined	undefined	null	Error object	null or Error object

Key Moments - 3 Insights

Why is 'pending' true before data arrives?

'pending' is true during the fetch promise to indicate loading, as shown in execution_table step 1 and 2.

What happens if the fetch fails?

If fetch fails, 'error' stores the error object and 'data' becomes null, shown in step 5 of execution_table.

Why does the component re-render after data arrives?

Because 'data' changes from undefined to the fetched array, triggering reactive updates and re-render (step 3 and 4).

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'pending' at step 3?

A false

B true

C undefined

D null

💡 Hint

Check the 'State After' column at step 3 in execution_table.

At which step does the component render the fetched data?

A Step 1

B Step 2

C Step 4

D Step 5

💡 Hint

Look for 'Render data list' or 'Data visible on screen' in execution_table.

If the fetch fails, what happens to the 'data' variable?

A It becomes an empty array

B It becomes null

C It stays undefined

D It keeps previous data

💡 Hint

See execution_table step 5 and variable_tracker for 'data' changes on error.

Concept Snapshot

Nuxt data fetching uses useFetch or useAsyncData.
Call them in setup to start async fetch.
They return reactive data, pending, and error states.
Component renders loading while pending is true.
On success, data updates and component re-renders.
On error, error state updates and shows error UI.

Full Transcript

In Nuxt, you fetch data inside components using useFetch or useAsyncData. When the component starts, these functions begin fetching data asynchronously. While waiting, the 'pending' state is true, so the component can show a loading message. When the data arrives successfully, 'pending' becomes false and 'data' holds the fetched result. The component then re-renders to show the data. If the fetch fails, 'error' holds the error details and the component shows an error message. This flow ensures the UI updates automatically based on fetch status.