Shared state across layouts in NextJS - Step-by-Step Execution

Concept Flow - Shared state across layouts

User interacts with page

↓

Layout component reads shared state

↓

Shared state updated via React context or server component

↓

All layouts consuming state re-render

↓

Page content updates reflecting shared state

User actions update shared state stored in a common provider, layouts consume this state and update UI accordingly.

Execution Sample

NextJS

import { createContext, useState, useContext } from 'react';

const SharedStateContext = createContext();

export function SharedStateProvider({ children }) {
  const [count, setCount] = useState(0);
  return <SharedStateContext.Provider value={{ count, setCount }}>{children}</SharedStateContext.Provider>;
}

export function useSharedState() {
  return useContext(SharedStateContext);
}

This code creates a React context to hold shared state and provides hooks to access and update it across layouts.

Execution Table

Step	Action	State Before	State After	Effect on Layouts
1	Initial render	count=0	count=0	Layouts render with count=0
2	User clicks increment button	count=0	count=1	Layouts re-render showing count=1
3	User clicks increment button again	count=1	count=2	Layouts re-render showing count=2
4	User navigates to another page with same layout	count=2	count=2	Layouts show count=2, state preserved
5	User clicks decrement button	count=2	count=1	Layouts re-render showing count=1
6	Exit	count=1	count=1	User leaves, state remains until reset or reload

💡 Execution stops when user leaves or reloads page; shared state persists during session.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	Final
count	0	1	2	1	1

Key Moments - 3 Insights

Why do all layouts update when the shared state changes?

Because the shared state is stored in a React context provider wrapping all layouts, any update triggers re-render in all consuming layouts as shown in steps 2, 3, and 5.

Does the shared state reset when navigating between pages?

No, the shared state persists across page navigation because the provider wraps the entire app layout, as seen in step 4 where count remains 2.

What happens if the provider is not wrapping all layouts?

Layouts outside the provider won't access or update the shared state, so they won't reflect changes, breaking shared state behavior.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'count' after step 3?

A 2

B 1

C 0

D 3

💡 Hint

Check the 'State After' column for step 3 in the execution table.

At which step does the shared state persist across page navigation?

A Step 2

B Step 5

C Step 4

D Step 6

💡 Hint

Look for the step mentioning navigation and state preservation in the execution table.

If the provider was removed, what would happen to the layouts?

A They would still share state normally.

B They would not update on state changes.

C They would crash immediately.

D They would update only on page reload.

💡 Hint

Refer to the key moment about provider wrapping all layouts.

Concept Snapshot

Shared state across layouts in Next.js uses React context or server components.
Wrap your app or layouts with a provider holding state.
Layouts consume this state via hooks to stay in sync.
State persists across page navigation within the provider.
Updates trigger re-render in all layouts consuming the state.

Full Transcript

In Next.js, to share state across different layouts, you create a React context provider that holds the shared state. This provider wraps the entire app or the layouts that need access. When the user interacts and updates the state, all layouts consuming this context re-render to reflect the new state. The shared state persists across page navigation as long as the provider remains mounted. This approach ensures consistent UI updates and state synchronization across layouts.

Practice

1. What is the main benefit of sharing state across layouts in Next.js?

easy

A. It allows multiple layouts and pages to access the same data easily.

B. It improves the styling of components automatically.

C. It speeds up the server response time by caching data.

D. It prevents users from navigating between pages.

Solution

1. Step 1: Understand the purpose of shared state

   Shared state means multiple parts of the app can use the same data without duplication.

2. Step 2: Identify the benefit in Next.js layouts

   Sharing state across layouts lets pages and layouts access common data easily, improving consistency.

3. Final Answer:

   It allows multiple layouts and pages to access the same data easily. -> Option A

4. Quick Check:

   Shared state = common data access [OK]

Hint: Shared state means one data source for many layouts [OK]

Common Mistakes:

• Confusing shared state with styling or caching
• Thinking shared state blocks navigation
• Assuming shared state only affects server speed

2. Which of the following is the correct way to provide shared state in Next.js layouts using React Context?

easy

A. Import state from a CSS file and use it in layouts.

B. Wrap the root layout with a Context Provider component.

C. Use getServerSideProps to pass state to layouts.

D. Add state variables directly inside each layout without a provider.

Solution

1. Step 1: Recall React Context usage

   React Context requires wrapping components with a Provider to share state.

2. Step 2: Apply to Next.js layouts

   Wrapping the root layout with the Provider shares state across all nested layouts and pages.

3. Final Answer:

   Wrap the root layout with a Context Provider component. -> Option B

4. Quick Check:

   Provider wraps root layout = shared state [OK]

Hint: Always wrap root layout with Provider for shared state [OK]

Common Mistakes:

• Trying to add state without a Provider
• Using server props instead of Context for shared state
• Confusing CSS imports with state management

3. Given this code snippet in a Next.js app, what will be the output when clicking the button in any nested layout?

const CountContext = React.createContext();

function CountProvider({ children }) {
  const [count, setCount] = React.useState(0);
  return (
    <CountContext.Provider value={{ count, setCount }}>
      {children}
    </CountContext.Provider>
  );
}

function Button() {
  const { count, setCount } = React.useContext(CountContext);
  return <button onClick={() => setCount(count + 1)}>Clicked {count} times</button>;
}

// Root layout wraps children with <CountProvider>

medium

A. Clicking the button increases the count visible in all layouts sharing the context.

B. Clicking the button only updates the count inside the Button component itself.

C. Clicking the button causes a runtime error because context is not provided.

D. Clicking the button resets the count to zero every time.

Solution

1. Step 1: Understand context sharing

   The CountProvider shares count state via context to all nested components.

2. Step 2: Analyze button behavior

   Clicking the button calls setCount to increase count, updating all components using the context.

3. Final Answer:

   Clicking the button increases the count visible in all layouts sharing the context. -> Option A

4. Quick Check:

   Context state update = shared count change [OK]

Hint: Context updates reflect everywhere wrapped by Provider [OK]

Common Mistakes:

• Thinking state updates are local to Button only
• Assuming missing Provider causes error here
• Believing count resets on each click

4. You have wrapped your root layout with a Context Provider, but nested layouts cannot access the shared state. What is the most likely cause?

medium

A. You placed the Provider inside a nested layout instead of the root layout.

B. You used React.useState instead of React.useContext in the root layout.

C. You forgot to use the custom hook or React.useContext inside nested layouts.

D. You imported the context from a CSS file instead of a JavaScript file.

Solution

1. Step 1: Check how nested layouts access context

   Nested layouts must use React.useContext or a custom hook to read shared state.

2. Step 2: Identify common mistake

   Forgetting to call useContext means no access to the shared data, even if Provider is correct.

3. Final Answer:

   You forgot to use the custom hook or React.useContext inside nested layouts. -> Option C

4. Quick Check:

   Missing useContext call = no access [OK]

Hint: Use useContext hook inside nested layouts to access shared state [OK]

Common Mistakes:

• Placing Provider too deep, not at root
• Confusing useState with useContext
• Importing context incorrectly from non-JS files

5. You want to share a user authentication state across multiple layouts in Next.js. Which approach correctly combines shared state with server-side data fetching to keep the user logged in?

hard

A. Use local component state in each layout to store user info fetched from the server on mount.

B. Store user data only in getServerSideProps and pass it as props to each layout without using Context.

C. Save user info in a CSS variable and read it in layouts for shared state.

D. Wrap the root layout with a Context Provider that holds user state, and update it client-side after fetching user info in a server action or API route.

Solution

1. Step 1: Understand combining server data with shared state

   User info fetched server-side should be stored in a shared client state for consistent access.

2. Step 2: Use Context Provider at root layout

   Wrapping root layout with a Provider holding user state allows all layouts to access and update it.

3. Step 3: Update state client-side after server fetch

   Fetching user info via server actions or API routes and updating context keeps user logged in across layouts.

4. Final Answer:

   Wrap the root layout with a Context Provider that holds user state, and update it client-side after fetching user info in a server action or API route. -> Option D

5. Quick Check:

   Context + server fetch = shared auth state [OK]

Hint: Use Context Provider plus server fetch to share auth state [OK]

Common Mistakes:

• Passing user data only via props without shared state
• Using local state per layout causing inconsistent user info
• Trying to store user info in CSS or non-JS files