[Solved] Given this Remix loader code running on an edge deployment target:export async function loader() { const data = await... }What is a likely architectural consideration for this deployment? | Remix

Remix - Deployment

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?

AThe loader must use local database queries only

BThe loader can run server-side and fetch data directly from the API

CThe loader cannot use async functions on edge

DThe loader must run in the browser and cannot fetch server data

Step-by-Step Solution

Solution:

Step 1: Understand edge deployment context
Edge deployment runs code close to users but still server-side, so loaders run on the server.
Step 2: Analyze loader data fetching
The loader can fetch data from external APIs directly because it runs server-side on the edge.
Final Answer:
The loader can run server-side and fetch data directly from the API -> Option B
Quick Check:
Edge loader fetches server-side = D [OK]

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

Common Mistakes:

MISTAKES

Master "Deployment" in Remix

9 interactive learning modes - each teaches the same concept differently

More Remix Quizzes

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