State synchronization patterns in NextJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a React state hook for a counter.

NextJS

const [count, [1]] = useState(0);

Drag options to blanks, or click blank then click option'

AupdateCount

BgetCount

CsetCount

DchangeCount

Attempts:

3 left

💡 Hint

Common Mistakes

Using a function name that does not start with 'set' for the updater.

Confusing the state variable with the updater function.

The useState hook returns a pair: the current state and a function to update it. The convention is to name the updater function starting with 'set'.

2fill in blank

medium

Complete the code to update the state when a button is clicked.

NextJS

<button onClick={() => [1](count + 1)}>Increment</button>

Drag options to blanks, or click blank then click option'

AsetCount

Bcount

CupdateCount

DchangeCount

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to assign directly to the state variable instead of using the updater.

Using the state variable name instead of the updater function.

To update the state, you call the updater function returned by useState. Here, setCount updates the count state.

3fill in blank

hard

Fix the error in the code to synchronize state with a server response using useEffect.

NextJS

useEffect(() => {
  fetch('/api/data')
    .then(res => res.json())
    .then(data => [1](data));
}, []);

Drag options to blanks, or click blank then click option'

Adata

BsetData

CupdateData

DfetchData

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to assign data directly to the state variable.

Calling a function that does not exist or is not the updater.

Inside useEffect, to update the React state with fetched data, you must call the updater function, here setData.

4fill in blank

hard

Fill both blanks to create a controlled input that updates state on change.

NextJS

<input type="text" value=[1] onChange={e => [2](e.target.value)} />

Drag options to blanks, or click blank then click option'

AinputValue

BsetInputValue

Cvalue

DsetValue

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different variable name for value and updater.

Not updating state on input change.

The value attribute should be bound to the state variable (inputValue), and the onChange handler should call the updater function (setInputValue) with the new input.

5fill in blank

hard

Fill all three blanks to create a memoized callback that updates state only when needed.

NextJS

const handleClick = useCallback(() => {
  [1]([2] + 1);
}, [[3]]);

Drag options to blanks, or click blank then click option'

AsetCount

Bcount

DupdateCount

Attempts:

3 left

💡 Hint

Common Mistakes

Not including the state variable in the dependency array.

Using the wrong function name for updating state.

The useCallback hook memoizes the function. Inside, you call the updater setCount with count + 1. The dependency array includes count to update the callback when count changes.

Practice

1. What is the main purpose of state synchronization in Next.js applications?

easy

A. To keep data consistent between server and client components

B. To improve CSS styling performance

C. To handle routing between pages

D. To optimize image loading speed

Solution

1. Step 1: Understand state synchronization concept

   State synchronization means keeping data the same across different parts of an app, especially between server and client.

2. Step 2: Identify Next.js usage

   Next.js apps often fetch data on the server and need to keep that data consistent on the client side.

3. Final Answer:

   To keep data consistent between server and client components -> Option A

4. Quick Check:

   State sync = consistent data [OK]

Hint: Think about data staying the same everywhere [OK]

Common Mistakes:

• Confusing state sync with styling or routing
• Thinking it only applies to client-side
• Assuming it improves image loading

2. Which of the following is the correct way to update a React state variable count using the useState hook in Next.js?

easy

A. updateCount(count + 1);

B. count = count + 1;

C. useState(count + 1);

D. setCount(count + 1);

Solution

1. Step 1: Recall useState update syntax

   React's useState returns a setter function to update state, e.g., setCount(newValue).

2. Step 2: Identify correct usage

   Direct assignment like count = count + 1 is invalid; useState(count + 1) is a hook call, not update; updateCount is undefined.

3. Final Answer:

   setCount(count + 1); -> Option D

4. Quick Check:

   useState setter = setCount() [OK]

Hint: Use the setter function from useState to update state [OK]

Common Mistakes:

• Trying to assign state variable directly
• Calling useState inside event handlers
• Using undefined update functions

3. Consider this Next.js component snippet:

import { useState, useEffect } from 'react';

export default function Counter() {
  const [count, setCount] = useState(0);

  useEffect(() => {
    const timer = setInterval(() => {
      setCount(c => c + 1);
    }, 1000);
    return () => clearInterval(timer);
  }, []);

  return <div>Count: {count}</div>;
}

What will the component display after 3 seconds?

medium

A. Count: 0

B. Count: 3

C. Count: 1

D. Count: NaN

Solution

1. Step 1: Understand useEffect with empty dependency

   The effect runs once on mount, setting an interval that increments count every 1000ms.

2. Step 2: Calculate count after 3 seconds

   After 3 intervals (3 seconds), count increments from 0 to 3.

3. Final Answer:

   Count: 3 -> Option B

4. Quick Check:

   Increment every second = 3 after 3s [OK]

Hint: Count increments once per second, so 3 seconds = 3 [OK]

Common Mistakes:

• Thinking useEffect runs multiple times
• Ignoring the cleanup function
• Assuming count resets

4. You have this Next.js component code that fetches data and sets state:

import { useState, useEffect } from 'react';

export default function DataFetcher() {
  const [data, setData] = useState(null);

  useEffect(() => {
    fetch('/api/data')
      .then(res => res.json())
      .then(json => setData(json));
  }, []);

  return <div>{data.title}</div>;
}

What error might occur when this component first renders?

medium

A. Infinite loop in useEffect

B. SyntaxError in fetch call

C. Cannot read property 'title' of null

D. setData is not a function

Solution

1. Step 1: Analyze initial state and render

   Initial state data is null, so on first render data.title tries to access property of null.

2. Step 2: Identify runtime error

   Accessing property on null causes a runtime error: "Cannot read property 'title' of null".

3. Final Answer:

   Cannot read property 'title' of null -> Option C

4. Quick Check:

   Access null.title = error [OK]

Hint: Check if state is null before accessing properties [OK]

Common Mistakes:

• Assuming fetch syntax error
• Expecting infinite loop without dependencies
• Confusing setData function availability

5. In Next.js, you want to synchronize server-fetched data with client state and update it on user interaction. Which pattern best achieves this?

hard

A. Fetch data in getServerSideProps, pass as props, then use useState on client to manage updates

B. Fetch data only on client with useEffect and ignore server data

C. Use getStaticProps and never update client state

D. Store data in a global variable outside React components

Solution

1. Step 1: Understand server and client data flow

   getServerSideProps fetches fresh data on each request, passing it as props to the component.

2. Step 2: Use client state for updates

   Using useState with initial props allows client-side updates while keeping initial server data.

3. Final Answer:

   Fetch data in getServerSideProps, pass as props, then use useState on client to manage updates -> Option A

4. Quick Check:

   Server props + client state = sync and update [OK]

Hint: Combine server props with client useState for sync and updates [OK]

Common Mistakes:

• Ignoring server data and fetching only on client
• Using static props without updates
• Using global variables outside React state