Shared state across layouts in NextJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is shared state across layouts in Next.js?

Shared state across layouts means keeping data or UI state consistent and accessible between different page layouts in a Next.js app, so changes in one layout reflect in others.

intermediate

How can you share state between layouts in Next.js using React Context?

You create a React Context provider at a high level (like in the root layout) and wrap your app with it. Then, any layout or page can access and update the shared state via the context.

beginner

Why is React Context preferred over prop drilling for shared state across layouts?

React Context avoids passing props through many layers, making code cleaner and easier to maintain when multiple layouts need the same state.

advanced

What role do Server Components play in shared state across layouts in Next.js 14+?

Server Components can fetch and provide data at the server level, which can then be passed as props to layouts. For dynamic client state, React Context or client components are still used.

intermediate

How does using a global store (like Zustand or Redux) help with shared state across layouts?

Global stores keep state outside React components, letting any layout or page subscribe to changes easily, ensuring consistent state without prop drilling or complex context nesting.

Which React feature is commonly used to share state across multiple layouts in Next.js?

A React Context

B React Hooks only

C Prop drilling

D CSS Modules

React Context provides a way to share state globally without passing props through many layers.

Where should you place the React Context provider to share state across all layouts in Next.js?

A In the root layout or app layout

B Inside each page component

C In a child component only

D In the public folder

Placing the provider in the root layout ensures all nested layouts and pages can access the shared state.

What is a downside of using prop drilling for shared state across layouts?

A It makes code simpler

B It can cause performance issues

C It requires passing props through many components

D It automatically updates all layouts

Prop drilling means passing props through many layers, which can make code hard to maintain.

Which of these is NOT a benefit of using a global state library like Zustand for shared state?

A Centralized state management

B Easy subscription to state changes

C Avoids prop drilling

D Automatic server-side rendering

Global state libraries help with client state but do not automatically handle server-side rendering.

In Next.js 14+, how do Server Components affect shared state management?

A They replace React Context completely

B They allow fetching data on the server to pass down as props

C They manage client-side UI state

D They prevent sharing state across layouts

Server Components fetch data on the server and pass it as props, but client state still uses React Context or other methods.

Explain how you would implement shared state across multiple layouts in a Next.js app.

Think about where to place the provider and how components access the state.

Describe the advantages and limitations of using React Context for shared state across layouts in Next.js.

Consider both benefits and performance aspects.

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