Internationalization (i18n) in Remix - Step-by-Step Execution

Concept Flow - Internationalization (i18n)

User visits page

↓

Detect user language

↓

Load language resources

↓

Render UI with translations

↓

User interacts

↓

Update UI if language changes

↓

Display content in chosen language

This flow shows how Remix detects user language, loads translations, and renders the UI accordingly.

Execution Sample

Remix

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

export async function loader({ request }) {
  const lang = request.headers.get('Accept-Language')?.split(',')[0].split('-')[0] || 'en';
  let messages;
  try {
    const mod = await import(`../locales/${lang}.json`);
    messages = mod.default;
  } catch {
    const mod = await import(`../locales/en.json`);
    messages = mod.default;
  }
  return json({ messages });
}

export default function Index() {
  const { messages } = useLoaderData();
  return <h1>{messages.title}</h1>;
}

This Remix loader detects the user's language, loads the correct translation file, and renders the title in that language.

Execution Table

Step	Action	Input/State	Output/Result
1	User visits page	Browser sends request with Accept-Language: 'fr, en;q=0.8'	Request received with headers
2	Loader reads Accept-Language header	'fr, en;q=0.8'	Extract language code 'fr'
3	Loader imports translation file	Import '../locales/fr.json'	Loaded messages object with French translations
4	Loader returns JSON response	messages object	Response contains messages for 'fr'
5	Component uses useLoaderData	Receives messages	messages available in component
6	Component renders <h1>	messages.title = 'Bonjour'	Page shows <h1>Bonjour</h1>
7	User changes browser language to 'en'	Next request Accept-Language: 'en'	Loader repeats steps with 'en' messages
8	Component renders updated title	messages.title = 'Hello'	Page shows <h1>Hello</h1>
9	No translation file found	Language 'es' requested but file missing	Fallback to default 'en' messages
10	Exit	All steps complete	Page shows content in correct language or fallback

💡 Execution stops after rendering page with correct or fallback language messages.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	Final
lang	undefined	'fr'	'fr'	'fr'	'fr'
messages	undefined	undefined	{title: 'Bonjour'}	{title: 'Bonjour'}	{title: 'Bonjour'}

Key Moments - 3 Insights

Why does the loader pick only the first language from Accept-Language header?

The loader uses split(',')[0] to get the primary language preference, ensuring it loads the most preferred translation first as shown in execution_table step 2.

What happens if the translation file for the detected language is missing?

As in execution_table step 9, the loader falls back to the default language (usually 'en') to avoid errors and still show content.

How does the component get the translation messages?

The component uses useLoaderData() to access the messages returned by the loader, as shown in execution_table step 5.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'lang' after step 2?

A 'fr'

B 'en'

C 'es'

D undefined

💡 Hint

Check the 'Action' and 'Output/Result' columns at step 2 in the execution_table.

At which step does the component render the translated title?

A Step 3

B Step 4

C Step 6

D Step 9

💡 Hint

Look for when the component uses messages to render UI in the execution_table.

If the translation file for 'es' is missing, what does the loader do?

A Throws an error and stops

B Falls back to default 'en' translations

C Loads 'fr' translations instead

D Returns empty messages

💡 Hint

Refer to step 9 in the execution_table about missing translation files.

Concept Snapshot

Internationalization (i18n) in Remix:
- Detect user language from request headers
- Load matching translation JSON file dynamically
- Pass translations via loader to component
- Render UI text using loaded messages
- Fallback to default language if missing
- Supports dynamic language switching

Full Transcript

This visual execution trace shows how Remix handles internationalization by detecting the user's preferred language from the Accept-Language header, loading the corresponding translation file, and rendering the UI with translated text. The loader function extracts the language code, imports the correct JSON file with messages, and passes them to the component via useLoaderData. The component then renders text like the page title in the chosen language. If a translation file is missing, Remix falls back to a default language to keep the app working. This process repeats on each request, allowing dynamic language support.

Practice

1. What is the main purpose of internationalization (i18n) in a Remix app?

easy

A. To improve app loading speed

B. To display app text in multiple languages based on user preference

C. To add animations to the user interface

D. To secure user data with encryption

Solution

1. Step 1: Understand the goal of i18n

   Internationalization means making your app support many languages so users see text in their own language.

2. Step 2: Match purpose to options

   Only To display app text in multiple languages based on user preference talks about showing text in multiple languages, which matches i18n's goal.

3. Final Answer:

   To display app text in multiple languages based on user preference -> Option B

4. Quick Check:

   i18n = multi-language support [OK]

Hint: i18n means multi-language text display [OK]

Common Mistakes:

• Confusing i18n with performance optimization
• Thinking i18n is about security
• Assuming i18n adds UI animations

2. Which of the following is the correct way to access a translation key using Remix loader data?

easy

A. const greeting = translations.get('greeting')

B. const greeting = useTranslation('greeting')

C. const greeting = i18n.t('greeting')

D. const greeting = loaderData.translations['greeting']

Solution

1. Step 1: Recall Remix loader data usage

   Loader functions return data accessed in components via loaderData. Translations are often passed this way.

2. Step 2: Identify correct syntax for translation access

   const greeting = loaderData.translations['greeting'] uses loaderData.translations['greeting'], which is valid JavaScript to get a translation string.

3. Final Answer:

   const greeting = loaderData.translations['greeting'] -> Option D

4. Quick Check:

   Access translations via loaderData object [OK]

Hint: Use loaderData to get translations in Remix [OK]

Common Mistakes:

• Using React hooks like useTranslation inside loaders
• Calling i18n.t() without importing or context
• Trying to get translations directly without loader data

3. Given this Remix loader code snippet:

export async function loader({ request }) {
  const lang = detectLanguage(request);
  const translations = await loadTranslations(lang);
  return { translations };
}

What will loaderData.translations.greeting contain if the user's language is Spanish and the translation file has { "greeting": "Hola" }?

medium

A. "Hola"

B. "Hello"

C. undefined

D. An error will occur

Solution

1. Step 1: Understand language detection and loading

   The loader detects Spanish and loads Spanish translations, which include greeting: "Hola".

2. Step 2: Check returned translations object

   The loader returns translations with greeting key set to "Hola", so loaderData.translations.greeting is "Hola".

3. Final Answer:

   "Hola" -> Option A

4. Quick Check:

   Detected Spanish language returns "Hola" [OK]

Hint: Loader returns translations matching detected language [OK]

Common Mistakes:

• Assuming default English text is returned
• Expecting undefined if language is Spanish
• Thinking loaderData is empty or causes error

4. You wrote this Remix loader to get translations:

export async function loader({ request }) {
  const lang = detectLanguage(request);
  const translations = loadTranslations(lang);
  return { translations };
}

Why might this cause a problem when running the app?

medium

A. Because loadTranslations is missing await, so translations is a Promise

B. Because detectLanguage cannot read the request object

C. Because loader functions cannot return objects

D. Because translations should be imported, not loaded dynamically

Solution

1. Step 1: Check async function usage

   loadTranslations is async, so it returns a Promise. Missing await means translations is a Promise, not resolved data.

2. Step 2: Understand impact on returned data

   Returning a Promise instead of actual translations causes errors or unexpected behavior in components.

3. Final Answer:

   Because loadTranslations is missing await, so translations is a Promise -> Option A

4. Quick Check:

   Async calls need await in loaders [OK]

Hint: Always await async calls in loaders [OK]

Common Mistakes:

• Forgetting to await async functions
• Assuming detectLanguage fails on request
• Thinking loaders can't return objects

5. You want to support English and French in your Remix app. You have translation files:

en.json: { "welcome": "Welcome" }
fr.json: { "welcome": "Bienvenue" }

How should you structure your loader and component to show the correct welcome message based on user language?

hard

A. Load both translation files in loader and merge them; in component, always show English welcome

B. In component, detect language and load translations; in loader, return empty object

C. In loader, detect language and load translations; in component, use loaderData.translations['welcome'] to display text

D. Hardcode welcome message in component and ignore loader

Solution

1. Step 1: Use loader to detect language and load correct translations

   The loader should detect user language and load only that language's translations to send to the component.

2. Step 2: Use component to display translation from loaderData

   The component accesses loaderData.translations['welcome'] to show the correct message dynamically.

3. Final Answer:

   In loader, detect language and load translations; in component, use loaderData.translations['welcome'] to display text -> Option C

4. Quick Check:

   Loader detects language, component shows translation [OK]

Hint: Detect language in loader, display translations in component [OK]

Common Mistakes:

• Loading translations in component instead of loader
• Merging all languages and ignoring user preference
• Hardcoding text instead of using translations