Why deployment target shapes architecture in Remix - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Remix loader function that fetches data.

Remix

export async function loader({ request }) {
  const data = await fetch([1]);
  return data.json();
}

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

A'/api/data'

B'/styles/main.css'

C'/favicon.ico'

D'/images/logo.png'

Attempts:

3 left

💡 Hint

Common Mistakes

Using a static asset URL instead of an API endpoint.

Forgetting to await the fetch call.

The loader function fetches data from an API endpoint, so the URL should point to '/api/data'.

2fill in blank

medium

Complete the code to export a Remix action function that handles form submission.

Remix

export async function action({ request }) {
  const formData = await request.[1]();
  // process formData
}

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

Atext

BformData

Cjson

Dblob

Attempts:

3 left

💡 Hint

Common Mistakes

Using request.json() instead of request.formData().

Not awaiting the formData call.

The action function processes form submissions, so it uses request.formData() to get the form data.

3fill in blank

hard

Fix the error in the Remix route component by correctly importing the useLoaderData hook.

Remix

import { [1] } from '@remix-run/react';

export default function RouteComponent() {
  const data = useLoaderData();
  return <div>{data.message}</div>;
}

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

AuseRouteData

BuseActionData

CuseLoaderData

DuseData

Attempts:

3 left

💡 Hint

Common Mistakes

Importing useActionData instead of useLoaderData.

Using a non-existent hook like useRouteData.

The hook to access loader data in Remix is useLoaderData from '@remix-run/react'.

4fill in blank

hard

Fill both blanks to create a Remix route that uses a loader and returns JSON response.

Remix

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

export async function loader() {
  const data = await fetch('/api/info');
  const jsonData = await data.[1]();
  return [2](jsonData);
}

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

Ajson

Btext

Dredirect

Attempts:

3 left

💡 Hint

Common Mistakes

Parsing response incorrectly or returning raw fetch response.

Using redirect instead of json for data response.

First, we parse the fetch response as JSON, then wrap it with Remix's json() to return a JSON response.

5fill in blank

hard

Fill all three blanks to define a Remix route with loader, action, and default component.

Remix

import { json } from '@remix-run/node';
import { useLoaderData } from '@remix-run/react';

export async function loader() {
  return [1]({ message: 'Hello from loader' });
}

export async function action({ request }) {
  const form = await request.[2]();
  const name = form.get('name');
  return [3]({ greeting: `Hello, ${name}` });
}

export default function Greeting() {
  const data = useLoaderData();
  return <div>{data.message}</div>;
}

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

Ajson

BformData

Dtext

Attempts:

3 left

💡 Hint

Common Mistakes

Using text() instead of json() for responses.

Not awaiting request.formData() in action.

The loader returns JSON using Remix's json(). The action reads formData and returns JSON greeting.

Practice

1. Why does the deployment target influence the architecture of a Remix app?

easy

A. Because it determines where the code runs and how data is fetched

B. Because it changes the programming language Remix uses

C. Because it decides the color scheme of the app

D. Because it controls the font sizes in the UI

Solution

1. Step 1: Understand deployment target meaning

   The deployment target is where your app's code runs, like a server or edge.

2. Step 2: Connect deployment to architecture

   Where code runs affects how you fetch data and structure your app to work efficiently.

3. Final Answer:

   Because it determines where the code runs and how data is fetched -> Option A

4. Quick Check:

   Deployment target shapes architecture = C [OK]

Hint: Think where your code runs to know architecture needs [OK]

Common Mistakes:

• Confusing deployment target with UI design
• Thinking deployment changes programming language
• Ignoring data fetching impact

2. Which of the following is the correct way to specify a deployment target in Remix's remix.config.js?

easy

A. export default { server: 'node' }

B. export default { deploymentTarget: 'node' }

C. module.exports = { deploymentTarget: 'node' }

D. module.exports = { server: 'node' }

Solution

1. Step 1: Recall Remix config syntax

   Remix uses ES module syntax with export default in remix.config.js.

2. Step 2: Identify correct property for deployment target

   The correct property is server to specify the deployment target like 'node'.

3. Final Answer:

   export default { server: 'node' } -> Option A

4. Quick Check:

   Remix config uses export default with server key = A [OK]

Hint: Remember Remix config uses ES modules and 'server' key [OK]

Common Mistakes:

• Using CommonJS syntax (module.exports) instead of ES modules
• Using wrong property name like deploymentTarget
• Mixing export default with module.exports

3. Given this Remix loader code running on an edge deployment target:

export async function loader() {
  const data = await fetch('https://api.example.com/data');
  return data.json();
}

What is a likely architectural consideration for this deployment?

medium

A. The loader must use local database queries only

B. The loader can run server-side and fetch data directly from the API

C. The loader cannot use async functions on edge

D. The loader must run in the browser and cannot fetch server data

Solution

1. Step 1: Understand edge deployment context

   Edge deployment runs code close to users but still server-side, so loaders run on the server.

2. Step 2: Analyze loader data fetching

   The loader can fetch data from external APIs directly because it runs server-side on the edge.

3. Final Answer:

   The loader can run server-side and fetch data directly from the API -> Option B

4. Quick Check:

   Edge loader fetches server-side = D [OK]

Hint: Edge runs server-side code, so loaders fetch data directly [OK]

Common Mistakes:

• Thinking loaders run in the browser on edge
• Assuming async is not allowed on edge
• Believing loaders must use local DB only

4. You deployed a Remix app to a static hosting target but your loader function uses fetch to get server data. What is the likely problem?

medium

A. Static hosting automatically converts fetch to local calls

B. Loader runs server-side, so fetch works fine on static hosting

C. Loader cannot use fetch at all in Remix

D. Loader runs client-side on static hosting, so fetch may cause CORS errors

Solution

1. Step 1: Understand static hosting deployment

   Static hosting serves only static files; loaders run in the browser (client-side).

2. Step 2: Analyze fetch behavior client-side

   Client-side fetch to server APIs may cause CORS errors or expose secrets.

3. Final Answer:

   Loader runs client-side on static hosting, so fetch may cause CORS errors -> Option D

4. Quick Check:

   Static hosting loaders run client-side = A [OK]

Hint: Static hosting runs loaders client-side; watch for CORS [OK]

Common Mistakes:

• Assuming loaders always run server-side
• Ignoring CORS issues on client fetch
• Thinking static hosting changes fetch behavior

5. You want to optimize a Remix app deployed on a serverless platform. Which architectural change best suits this deployment target?

hard

A. Use persistent WebSocket connections for all data fetching

B. Store session data only in server memory

C. Minimize long-running server processes and use stateless loaders

D. Run all code in the browser to reduce server load

Solution

1. Step 1: Understand serverless platform traits

   Serverless platforms start and stop functions quickly; long processes and memory storage are limited.

2. Step 2: Choose architecture fitting serverless

   Stateless loaders and short executions fit serverless best; persistent connections and memory storage do not.

3. Final Answer:

   Minimize long-running server processes and use stateless loaders -> Option C

4. Quick Check:

   Serverless needs stateless, short tasks = B [OK]

Hint: Serverless = short, stateless functions, no long processes [OK]

Common Mistakes:

• Using persistent connections unsuitable for serverless
• Storing session data in server memory
• Thinking all code should run client-side