Redirect function in NextJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the redirect() function in Next.js?

The redirect() function in Next.js is used to send users to a different URL or page, often after an action like login or form submission. It helps control navigation programmatically.

intermediate

Where can you use the redirect() function in Next.js 14+?

You can use redirect() inside server components, server actions, and route handlers to perform server-side redirects before the page renders.

beginner

How do you import the <code>redirect()</code> function in a Next.js app router?

You import it from <code>next/navigation</code> like this: <br><code>import { redirect } from 'next/navigation'</code>

intermediate

What happens if you call redirect('/home') inside a server component?

The user is immediately sent to the '/home' page before the current page finishes rendering. The browser URL changes and the new page loads.

intermediate

Can you use redirect() inside client components in Next.js?

No, redirect() is meant for server-side use. For client-side navigation, use the useRouter() hook with router.push().

Where do you import the redirect() function from in Next.js?

A react-router-dom

B next/router

C next/redirect

D next/navigation

The redirect() function is imported from next/navigation in Next.js 14+.

What does calling redirect('/dashboard') inside a server component do?

A Navigates the user to '/dashboard' before rendering finishes

B Reloads the current page

C Shows an error message

D Does nothing on the server

Calling redirect() inside a server component sends the user to the new URL immediately.

Can you use redirect() inside a client component?

A Only with extra configuration

B Yes, it works the same

C No, use <code>router.push()</code> instead

D Only in development mode

The redirect() function is for server-side use. Client components should use router.push().

Which Next.js feature is commonly used together with redirect() for server-side logic?

A Server Actions

B Client Components

C Static Site Generation

D API Routes

redirect() is often used inside Server Actions to redirect after server-side tasks.

What is a common use case for redirect() in Next.js?

A Handling client-side events

B Redirecting after login or authentication

C Fetching data from API

D Styling components

redirect() is commonly used to send users to a new page after login or other server-side events.

Explain how the redirect() function works in Next.js and where you can use it.

Think about server vs client roles in Next.js.

Describe the difference between using redirect() and client-side navigation methods in Next.js.

Consider when the navigation happens and which environment runs the code.

Practice

1. What is the main purpose of the redirect function in Next.js?

easy

A. To fetch data from an API

B. To send users automatically to a different page

C. To style components dynamically

D. To create new server routes

Solution

1. Step 1: Understand the redirect function role

   The redirect function is designed to change the current page to another URL automatically.

2. Step 2: Compare with other options

   Fetching data, styling, or creating routes are unrelated to redirect's purpose.

3. Final Answer:

   To send users automatically to a different page -> Option B

4. Quick Check:

   Redirect = page navigation [OK]

Hint: Redirect means sending user to another page automatically [OK]

Common Mistakes:

• Confusing redirect with data fetching
• Thinking redirect styles components
• Assuming redirect creates routes

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

easy

A. import { redirect } from 'next/navigation'; redirect('/home');

B. import redirect from 'next/router'; redirect('/home');

C. import { redirect } from 'next/router'; redirect('/home');

D. import redirect from 'next/navigation'; redirect('/home');

Solution

1. Step 1: Identify correct import source

   The redirect function is imported from 'next/navigation' as a named import.

2. Step 2: Check usage syntax

   Calling redirect('/home') after import is correct usage.

3. Final Answer:

   import { redirect } from 'next/navigation'; redirect('/home'); -> Option A

4. Quick Check:

   Correct import and call from next/navigation [OK]

Hint: Use named import from 'next/navigation' for redirect [OK]

Common Mistakes:

• Importing redirect from 'next/router' instead
• Using default import instead of named import
• Calling redirect without importing

3. Consider this Next.js server component code snippet:

import { redirect } from 'next/navigation';

export default function Page() {
  const isLoggedIn = false;
  if (!isLoggedIn) {
    redirect('/login');
  }
  return <h1>Welcome</h1>;
}

What will the user see when visiting this page?

medium

A. A runtime error occurs

B. The user sees the text 'Welcome'

C. The page shows a blank screen

D. The user is redirected to '/login' page automatically

Solution

1. Step 1: Analyze the condition for redirect

   The variable isLoggedIn is false, so the condition !isLoggedIn is true, triggering redirect('/login').

2. Step 2: Understand redirect effect in server component

   Calling redirect sends the user to '/login' immediately, so the return statement is not reached.

3. Final Answer:

   The user is redirected to '/login' page automatically -> Option D

4. Quick Check:

   Redirect triggers when not logged in [OK]

Hint: If redirect runs, page content won't show [OK]

Common Mistakes:

• Thinking the return content still renders
• Assuming redirect causes error
• Ignoring the condition logic

4. This Next.js server component code has a mistake. What is the mistake?

import { redirect } from 'next/navigation';

export default function Page() {
  redirect('/dashboard');
  return <h1>Dashboard</h1>;
}

medium

A. Returning JSX after redirect call

B. Calling redirect outside a conditional or event handler

C. Using redirect in a client component

D. Missing async keyword on the function

Solution

1. Step 1: Understand redirect behavior

   Calling redirect immediately stops rendering and sends a redirect response.

2. Step 2: Check code after redirect call

   Returning JSX after redirect is invalid because redirect does not allow further rendering.

3. Final Answer:

   Returning JSX after redirect call -> Option A

4. Quick Check:

   Redirect stops rendering, no return allowed after [OK]

Hint: Do not return JSX after calling redirect [OK]

Common Mistakes:

• Thinking redirect can be called in client components
• Calling redirect without conditions is allowed
• Forgetting redirect stops rendering

5. You want to redirect users to '/profile' only if they are logged in, otherwise to '/login'. Which code correctly implements this logic in a Next.js server component?

hard

A. import { redirect } from 'next/navigation';

export default function Page() {
const loggedIn = true;
if (loggedIn) {
redirect('/login');
} else {
redirect('/profile');
}
return null;
}

B. import { redirect } from 'next/navigation';

export default function Page() {
const loggedIn = false;
if (loggedIn) {
redirect('/login');
} else {
redirect('/profile');
}
return null;
}

C. import { redirect } from 'next/navigation';

export default function Page() {
const loggedIn = false;
if (!loggedIn) {
redirect('/login');
} else {
redirect('/profile');
}
return null;
}

D. import { redirect } from 'next/navigation';

export default function Page() {
const loggedIn = true;
if (!loggedIn) {
redirect('/profile');
} else {
redirect('/login');
}
return null;
}

Solution

1. Step 1: Understand the logic needed

   If user is logged in, send to '/profile'; if not, send to '/login'.

2. Step 2: Match code logic with requirement

   import { redirect } from 'next/navigation'; export default function Page() { const loggedIn = false; if (!loggedIn) { redirect('/login'); } else { redirect('/profile'); } return null; } checks if not logged in, redirects to '/login', else to '/profile', matching the requirement.

3. Final Answer:

   Option C code correctly implements the redirect logic -> Option C

4. Quick Check:

   Redirect to login if not logged in, else profile [OK]

Hint: Redirect to login if NOT logged in, else profile [OK]

Common Mistakes:

• Swapping redirect URLs for logged in and not logged in
• Using wrong condition negation
• Returning JSX after redirect