Client-side session access in NextJS - Step-by-Step Execution

Concept Flow - Client-side session access

User visits page

↓

Browser loads React component

↓

Component runs useEffect

↓

Fetch session data from client-side API

↓

Session data received

↓

Update component state with session

↓

Component re-renders with session info

↓

User sees session-dependent UI

This flow shows how a Next.js React component fetches and uses session data on the client side after the page loads.

Execution Sample

NextJS

import { useState, useEffect } from 'react';
import { getSession } from 'next-auth/react';

export default function Profile() {
  const [session, setSession] = useState(null);
  useEffect(() => {
    getSession().then(data => setSession(data));
  }, []);
  return <div>{session ? `Hello, ${session.user.name}` : 'Loading...'}</div>;
}

This React component fetches the user session on the client side and shows a greeting or loading text.

Execution Table

Step	Action	Session State Before	Session State After	Component Output
1	Component mounts, useState initializes session=null	N/A	null	Displays 'Loading...'
2	useEffect runs, calls getSession()	null	null	Still 'Loading...'
3	getSession() resolves with session data	null	{ user: { name: 'Alice' } }	Triggers state update
4	setSession updates session state	null	{ user: { name: 'Alice' } }	Component re-renders
5	Component renders with session data	{ user: { name: 'Alice' } }	{ user: { name: 'Alice' } }	Displays 'Hello, Alice'
6	No further changes	{ user: { name: 'Alice' } }	{ user: { name: 'Alice' } }	Output stable

💡 Session data loaded and component shows user greeting; no more state changes.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
session	null	null	{ user: { name: 'Alice' } }	{ user: { name: 'Alice' } }	{ user: { name: 'Alice' } }

Key Moments - 2 Insights

Why does the component show 'Loading...' first before greeting the user?

Because the session state starts as null (see Step 1 and 2 in execution_table), so the UI shows 'Loading...' until getSession() fetches the data asynchronously.

What triggers the component to re-render with the session data?

When setSession updates the session state (Step 4), React re-renders the component to show the new session info (Step 5).

Visual Quiz - 3 Questions

Look at the execution table, what is the session state after Step 3?

A null

B { user: { name: 'Alice' } }

C undefined

D Loading...

💡 Hint

Check the 'Session State After' column for Step 3 in the execution_table.

At which step does the component output change from 'Loading...' to greeting the user?

A Step 2

B Step 3

C Step 5

D Step 6

💡 Hint

Look at the 'Component Output' column in execution_table for when the greeting appears.

If getSession() returned null (no session), what would the component display after Step 4?

A 'Loading...' or fallback UI

B 'Loading...'

C Empty string

D 'Hello, Alice'

💡 Hint

Refer to how the component renders when session is null in the code and execution_table Step 1 and 2.

Concept Snapshot

Client-side session access in Next.js:
- Use useEffect to fetch session after component mounts
- Use getSession() from next-auth/react to get session data
- Store session in useState to trigger re-render
- Show loading UI while session is null
- Update UI with user info once session loads

Full Transcript

This example shows how a Next.js React component accesses session data on the client side. When the component loads, it starts with session state as null, so it shows 'Loading...'. Then, inside useEffect, it calls getSession() asynchronously. When getSession() returns the session data, the component updates its state with setSession. This triggers a re-render, and the UI updates to greet the user by name. This flow ensures the session is accessed only on the client side after the page loads, avoiding server-side session access. The execution table traces each step, showing how the session state changes and how the component output updates accordingly.

Practice

1. What does the useSession hook from next-auth provide in a Next.js app?

easy

A. Access to the current user's session data and status on the client side

B. Server-side rendering of session data only

C. A way to store session data in local storage manually

D. Automatic user authentication without any configuration

Solution

1. Step 1: Understand the purpose of useSession

   The useSession hook is designed to provide session data and status on the client side in Next.js apps using next-auth.

2. Step 2: Compare options with the hook's functionality

   Access to the current user's session data and status on the client side correctly states it provides access to current user's session data and status. Other options describe unrelated or incorrect behaviors.

3. Final Answer:

   Access to the current user's session data and status on the client side -> Option A

4. Quick Check:

   useSession gives client session data = A [OK]

Hint: Remember: useSession is for client-side session info [OK]

Common Mistakes:

• Thinking useSession works only server-side
• Confusing useSession with local storage
• Assuming useSession auto-authenticates without setup

2. Which of the following is the correct way to import and use useSession in a Next.js component?

easy

A. import { useSession } from 'next-auth/client'; const session = useSession();

B. import useSession from 'next-auth/client'; const session = useSession();

C. import { useSession } from 'next-auth/react'; const session = useSession.data;

D. import { useSession } from 'next-auth/react'; const { data: session } = useSession();

Solution

1. Step 1: Check the correct import path and usage

   The official import for useSession in next-auth v4+ is from 'next-auth/react'. The hook returns an object with data and status.

2. Step 2: Validate the destructuring syntax

   import { useSession } from 'next-auth/react'; const { data: session } = useSession(); correctly imports and destructures data as session. Other options use wrong import paths or incorrect usage.

3. Final Answer:

   import { useSession } from 'next-auth/react'; const { data: session } = useSession(); -> Option D

4. Quick Check:

   Correct import and destructuring = C [OK]

Hint: Use 'next-auth/react' and destructure data as session [OK]

Common Mistakes:

• Importing from 'next-auth/client' which is outdated
• Not destructuring the returned object
• Accessing session data incorrectly

3. Given this Next.js component using useSession:

import { useSession } from 'next-auth/react';
export default function Profile() {
  const { data: session, status } = useSession();
  if (status === 'loading') return <p>Loading...</p>;
  if (!session) return <p>Not signed in</p>;
  return <p>Welcome, {session.user.name}!</p>;
}

What will be rendered if the user is signed in with name "Alex"?

medium

A. Not signed in

B. Loading...

C. Welcome, Alex!

D. Nothing is rendered

Solution

1. Step 1: Understand the session states

   The component shows "Loading..." if status is 'loading', "Not signed in" if no session, and welcome message if session exists.

2. Step 2: Apply the signed-in user condition

   Since the user is signed in with name "Alex", session exists and status is not 'loading'. So it renders the welcome message with the user's name.

3. Final Answer:

   <p>Welcome, Alex!</p> -> Option C

4. Quick Check:

   Signed-in user shows welcome message = A [OK]

Hint: Check session presence to show welcome, else loading or sign-in [OK]

Common Mistakes:

• Confusing loading and signed-in states
• Assuming session.user.name is undefined
• Ignoring the status check order

4. Identify the error in this Next.js component using useSession:

import { useSession } from 'next-auth/react';
export default function Dashboard() {
  const session = useSession();
  if (session.status === 'loading') return <p>Loading...</p>;
  if (!session.data) return <p>Please sign in</p>;
  return <p>Hello, {session.user.name}</p>;
}

medium

A. Accessing session.user.name directly instead of session.data.user.name

B. Incorrect import path for useSession

C. Missing useEffect to fetch session

D. Using session.status instead of session.state

Solution

1. Step 1: Check how useSession returns data

   useSession returns an object with data and status. The user info is inside data.user.

2. Step 2: Identify incorrect property access

   The code tries to access session.user.name directly, but it should be session.data.user.name. This causes an error.

3. Final Answer:

   Accessing session.user.name directly instead of session.data.user.name -> Option A

4. Quick Check:

   Use session.data.user for user info, not session.user [OK]

Hint: Remember session data is in session.data, not top-level [OK]

Common Mistakes:

• Accessing user info directly on session object
• Confusing status property names
• Adding unnecessary hooks like useEffect

5. You want to show a personalized greeting only if the user is signed in and their email is verified in the session. Given useSession returns { data: session, status }, which code snippet correctly implements this in a Next.js component?

hard

A. if (!session) return Please verify your email;
if (status === 'loading') return Loading...;
return Welcome back, {session.user.name}!;

B. if (status === 'loading') return Loading...;
if (!session || !session.user.emailVerified) return Please verify your email;
return Welcome back, {session.user.name}!;

C. if (status === 'loading') return Loading...;
if (!session.user.emailVerified) return Please verify your email;
return Welcome back, {session.user.name}!;

D. if (status === 'loading') return Loading...;
if (!session || session.user.emailVerified) return Please verify your email;
return Welcome back, {session.user.name}!;

Solution

1. Step 1: Check loading state first

   Always handle status === 'loading' first to avoid rendering before session is ready.

2. Step 2: Verify session existence and email verification

   We must check if session exists and if session.user.emailVerified is true. If not, show the verification message.

3. Step 3: Render personalized greeting if checks pass

   If session exists and email is verified, show welcome message with user name.

4. Final Answer:

   if (status === 'loading') return <p>Loading...</p>; if (!session || !session.user.emailVerified) return <p>Please verify your email</p>; return <p>Welcome back, {session.user.name}!</p>; -> Option B

5. Quick Check:

   Check loading, then session and emailVerified before greeting [OK]

Hint: Check loading first, then session and emailVerified [OK]

Common Mistakes:

• Checking session after loading state
• Not verifying session existence before accessing properties
• Incorrect logic for email verification condition