Protected routes with loaders in Remix - Mini Project: Build & Apply

Protected routes with loaders

📖 Scenario: You are building a simple web app using Remix. Some pages should only be visible to logged-in users. To do this, you will protect routes by checking user authentication in the loader function before rendering the page.

🎯 Goal: Create a protected route in Remix that uses a loader function to check if a user is logged in. If not logged in, redirect to the login page. If logged in, show the protected content.

📋 What You'll Learn

Create a loader function that checks for a user session

Use a config variable for the login redirect URL

Implement the core logic to redirect if no user is found

Complete the route component to display protected content

💡 Why This Matters

🌍 Real World

Protecting pages in web apps to ensure only logged-in users can access sensitive content is a common need.

💼 Career

Understanding route protection with loaders is essential for building secure Remix applications in professional web development.

1

Create a loader function with a user session check

Create a loader function that accepts { request } as a parameter. Inside, create a variable called user and set it to null to simulate no user logged in yet.

Remix

export async function loader({ request }) {
  // Your code here
}

Hint

Start by defining the loader function and a user variable set to null.

2

Add a config variable for the login redirect URL

Add a constant called LOGIN_REDIRECT and set it to the string "/login" above the loader function.

Remix

const LOGIN_REDIRECT = "/login";

export async function loader({ request }) {
  const user = null;
  // Your code here
}

Hint

Define a constant string for the login redirect path.

3

Redirect to login if user is not authenticated

Inside the loader function, add an if statement that checks if user is null. If so, return a redirect response to LOGIN_REDIRECT using redirect(LOGIN_REDIRECT). Import redirect from @remix-run/node at the top.

Remix

import { redirect } from "@remix-run/node";

const LOGIN_REDIRECT = "/login";

export async function loader({ request }) {
  const user = null;
  // Your code here
}

Hint

Use the redirect function to send users to the login page if not logged in.

4

Complete the route component to show protected content

Add a default export function component called ProtectedPage that returns a simple <div> with the text "Welcome to the protected page!".

Remix

import { redirect } from "@remix-run/node";

const LOGIN_REDIRECT = "/login";

export async function loader({ request }) {
  const user = null;
  if (user === null) {
    return redirect(LOGIN_REDIRECT);
  }
}

// Your code here

Hint

Define the React component that shows the protected content.

Practice

1. What is the main purpose of using a loader in a protected route in Remix?

easy

A. To check if the user is authorized before showing the page

B. To style the page with CSS

C. To fetch data after the page is rendered

D. To handle button clicks on the page

Solution

1. Step 1: Understand the role of loaders in Remix

   Loaders run before the page renders and can check user permissions.

2. Step 2: Identify the purpose of protected routes

   Protected routes restrict access to authorized users only, so loaders check authorization.

3. Final Answer:

   To check if the user is authorized before showing the page -> Option A

4. Quick Check:

   Loader checks authorization = To check if the user is authorized before showing the page [OK]

Hint: Loaders run before page render to check access [OK]

Common Mistakes:

• Thinking loaders style pages
• Assuming loaders run after rendering
• Confusing loaders with event handlers

2. Which of the following is the correct way to redirect unauthorized users inside a Remix loader?

easy

A. navigate('/login')

B. return redirect('/login')

C. throw redirect('/login')

D. window.location.href = '/login'

Solution

1. Step 1: Recall Remix loader redirect syntax

   In Remix loaders, you use throw redirect() to redirect users.

2. Step 2: Compare options

   throw redirect('/login') uses throw redirect('/login'), which is the correct Remix pattern.

3. Final Answer:

   throw redirect('/login') -> Option C

4. Quick Check:

   Use throw redirect() in loaders = throw redirect('/login') [OK]

Hint: Use throw redirect() inside loaders for redirects [OK]

Common Mistakes:

• Using return redirect() instead of throw
• Using client-side navigation methods in loaders
• Trying to set window.location in server code

3. Given this loader code in Remix, what happens if the user is not logged in?

import { redirect } from '@remix-run/node';

export async function loader({ request }) {
  const user = await getUser(request);
  if (!user) {
    throw redirect('/login');
  }
  return { user };
}

medium

A. The loader returns null and the page is blank

B. The user sees the protected page with user data

C. The page shows an error message but stays on the same URL

D. The user is redirected to the /login page

Solution

1. Step 1: Analyze the loader logic

   If user is falsy (not logged in), the loader throws redirect('/login').

2. Step 2: Understand Remix redirect behavior

   Throwing redirect sends the browser to the specified URL before rendering the page.

3. Final Answer:

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

4. Quick Check:

   Throw redirect sends user away = The user is redirected to the /login page [OK]

Hint: Throw redirect sends user to new page before render [OK]

Common Mistakes:

• Thinking user sees protected page anyway
• Assuming error message shows instead of redirect
• Believing loader returns null means blank page

4. Identify the error in this Remix loader for a protected route:

import { redirect } from '@remix-run/node';

export async function loader({ request }) {
  const user = await getUser(request);
  if (!user) {
    return redirect('/login');
  }
  return { user };
}

medium

A. Missing await before getUser(request)

B. Using return redirect() instead of throw redirect() causes a runtime error

C. Loader should not return user data

D. redirect should be imported from '@remix-run/react'

Solution

1. Step 1: Check redirect usage in loader

   In Remix loaders, you must throw redirect(), not return it.

2. Step 2: Understand consequences of return redirect()

   Returning redirect() does not stop loader execution properly and causes errors.

3. Final Answer:

   Using return redirect() instead of throw redirect() causes a runtime error -> Option B

4. Quick Check:

   Throw redirect required in loaders = Using return redirect() instead of throw redirect() causes a runtime error [OK]

Hint: Always throw redirect() in loaders, never return it [OK]

Common Mistakes:

• Returning redirect() instead of throwing
• Importing redirect from wrong package
• Forgetting async/await on getUser

5. You want to protect a route so only logged-in users can access it. You also want to fetch user profile data in the loader. Which is the best way to write the loader?

import { redirect } from '@remix-run/node';

export async function loader({ request }) {
  const user = await getUser(request);
  if (!user) {
    throw redirect('/login');
  }
  const profile = await getUserProfile(user.id);
  return { user, profile };
}

hard

A. This loader correctly protects the route and fetches profile data

B. You should fetch profile data before checking user to avoid errors

C. You must return redirect('/login') instead of throwing it

D. Loaders cannot fetch multiple data items; split into two loaders

Solution

1. Step 1: Check authorization logic

   The loader checks if user exists, and throws redirect if not, protecting the route.

2. Step 2: Confirm data fetching after authorization

   Fetching profile after confirming user is safe and logical.

3. Step 3: Validate return structure

   Returning both user and profile data together is valid and useful for the page.

4. Final Answer:

   This loader correctly protects the route and fetches profile data -> Option A

5. Quick Check:

   Check user, throw redirect, then fetch data = This loader correctly protects the route and fetches profile data [OK]

Hint: Check user first, then fetch data, throw redirect if unauthorized [OK]

Common Mistakes:

• Fetching data before checking user
• Returning redirect instead of throwing
• Splitting data fetching unnecessarily