Protected routes with loaders in Remix - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the redirect function from Remix.

Remix

import { [1] } from "@remix-run/node";

Drag options to blanks, or click blank then click option'

ALink

BuseLoaderData

COutlet

Dredirect

Attempts:

3 left

💡 Hint

Common Mistakes

Importing useLoaderData instead of redirect.

Importing from the wrong package.

The redirect function is imported from @remix-run/node to redirect unauthenticated users.

2fill in blank

medium

Complete the loader function to check if the user is authenticated.

Remix

export const loader = async ({ request }) => {
  const user = await getUserFromRequest([1]);
  if (!user) {
    throw redirect('/login');
  }
  return json({ user });
};

Drag options to blanks, or click blank then click option'

Arequest

Bresponse

Cparams

Dcontext

Attempts:

3 left

💡 Hint

Common Mistakes

Using response instead of request.

Using undefined variables like params or context.

The request object contains information about the HTTP request and is used to get the user session.

3fill in blank

hard

Fix the error in the loader to correctly redirect unauthenticated users.

Remix

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

export const loader = async ({ request }) => {
  const user = await getUserFromRequest(request);
  if (!user) {
    [1]('/login');
  }
  return json({ user });
};

Drag options to blanks, or click blank then click option'

Athrow

Bredirect

Cthrow redirect

Dreturn redirect

Attempts:

3 left

💡 Hint

Common Mistakes

Returning redirect() instead of throwing it.

Throwing a string or other value instead of the redirect.

In Remix loaders, to redirect, you must throw the redirect() call, not just return it.

4fill in blank

hard

Fill both blanks to use the loader data and render the user's name.

Remix

import { useLoaderData } from "@remix-run/react";

export default function Profile() {
  const data = useLoaderData();
  return <div>Welcome, [1]. Your email is [2].</div>;
}

Drag options to blanks, or click blank then click option'

Adata.user.name

Bdata.user.email

Cuser.name

Duser.email

Attempts:

3 left

💡 Hint

Common Mistakes

Using user.name directly without data.

Mixing up name and email fields.

The useLoaderData() hook returns the data object from the loader, so you access data.user.name and data.user.email.

5fill in blank

hard

Fill all three blanks to create a protected route with loader and render user info.

Remix

import { json, [1] } from "@remix-run/node";
import { useLoaderData } from "@remix-run/react";

export const loader = async ({ request }) => {
  const user = await getUserFromRequest(request);
  if (!user) {
    [2]('/login');
  }
  return json({ user });
};

export default function Dashboard() {
  const { user } = useLoaderData();
  return <main>Hello, [3]!</main>;
}

Drag options to blanks, or click blank then click option'

Aredirect

Bthrow redirect

Cuser.name

Djson

Attempts:

3 left

💡 Hint

Common Mistakes

Returning redirect instead of throwing it.

Not importing redirect.

Trying to access user data incorrectly.

Import redirect to redirect unauthenticated users. In the loader, throw redirect('/login') is used to redirect. In the component, display the user's name with user.name.

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