Locale detection strategies in NextJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is locale detection in Next.js?

Locale detection is the process Next.js uses to find out the user's language or region preference to show content in the right language automatically.

beginner

Name two common ways Next.js detects a user's locale.

1. Using the browser's Accept-Language header sent with requests.
2. Checking the URL path or subdomain for locale info.

intermediate

How does Next.js use the Accept-Language header for locale detection?

Next.js reads the Accept-Language header from the browser request to guess the user's preferred language and serve the matching locale content.

intermediate

What role does URL routing play in locale detection in Next.js?

Next.js can use locale prefixes in URLs (like /en or /fr) to detect and serve content in the correct language based on the URL path.

intermediate

Why might you want to store the detected locale in a cookie or local storage?

Storing the locale helps remember the user's language choice for future visits, improving user experience by avoiding repeated detection or defaulting to wrong languages.

Which HTTP header does Next.js commonly use to detect user locale?

A Accept-Language

B Content-Type

C User-Agent

D Authorization

The Accept-Language header tells the server the user's preferred languages.

What is a common URL pattern to indicate locale in Next.js?

A /en

B /language=en

C /locale/en

D /lang/en

Next.js uses locale prefixes like /en or /fr directly in the URL path.

Why is storing locale in a cookie useful?

A To speed up page loading

B To remember user language choice across visits

C To improve SEO rankings

D To block unwanted users

Cookies help remember user preferences like language for future visits.

Which Next.js feature helps automatically detect and serve locales?

A Image optimization

B API routes

C Static generation

D Middleware

Middleware can inspect requests and detect locale before rendering.

If no locale is detected, what does Next.js usually do?

A Show an error page

B Ask user to select language

C Serve content in English by default

D Redirect to homepage

Next.js typically falls back to a default locale like English.

Explain how Next.js detects a user's locale using the Accept-Language header and URL routing.

Think about how the browser sends language info and how URLs can show language.

Describe why storing the detected locale in cookies or local storage improves user experience in Next.js apps.

Consider what happens when a user returns to the site.

Practice

1. What is the main purpose of locale detection in a Next.js application?

easy

A. To change the website layout based on screen size

B. To improve server response time by caching pages

C. To track user clicks for analytics

D. To automatically show the website in the user's preferred language

Solution

1. Step 1: Understand locale detection purpose

   Locale detection is used to identify the user's language preference automatically.

2. Step 2: Match purpose to options

   Showing the website in the user's preferred language matches the purpose of locale detection.

3. Final Answer:

   To automatically show the website in the user's preferred language -> Option D

4. Quick Check:

   Locale detection = show preferred language [OK]

Hint: Locale detection means showing language automatically [OK]

Common Mistakes:

• Confusing locale detection with performance optimization
• Thinking it changes layout instead of language
• Mixing locale detection with analytics tracking

2. Which Next.js feature is commonly used to configure supported locales for automatic detection?

easy

A. next.config.js i18n field

B. pages/api/locale.js file

C. Custom _document.js file

D. Static CSS files

Solution

1. Step 1: Identify where locale config is set

   Next.js uses the i18n field inside next.config.js to define supported locales.

2. Step 2: Check other options

   API files, _document.js, and CSS files do not configure locales.

3. Final Answer:

   next.config.js i18n field -> Option A

4. Quick Check:

   Locale config = next.config.js i18n [OK]

Hint: Locales go in next.config.js under i18n [OK]

Common Mistakes:

• Trying to configure locales in API routes
• Using _document.js for locale settings
• Assuming CSS files control language

3. Given this middleware snippet in Next.js, what happens when a user with 'fr' browser language visits the site?

export function middleware(request) {
  const locale = request.headers.get('accept-language')?.split(',')[0].split('-')[0];
  if (locale === 'fr') {
    return Response.redirect(new URL('/fr', request.url));
  }
  return Response.next();
}

medium

A. User is redirected to the homepage

B. User is redirected to the /fr page

C. User gets a 404 error

D. User stays on the current page without redirect

Solution

1. Step 1: Analyze locale extraction from headers

   The code extracts the first language code from the 'accept-language' header, e.g., 'fr'.

2. Step 2: Check redirect condition

   If locale is 'fr', the middleware redirects to '/fr' URL.

3. Final Answer:

   User is redirected to the /fr page -> Option B

4. Quick Check:

   Locale 'fr' triggers redirect to /fr [OK]

Hint: Check header locale then redirect if matches [OK]

Common Mistakes:

• Ignoring the redirect and assuming no change
• Confusing header parsing logic
• Assuming redirect to homepage always

4. Identify the error in this Next.js middleware code for locale detection:

export function middleware(request) {
  const locale = request.headers.get('accept-language').split(',')[0];
  if (locale === 'en') {
    return Response.redirect(new URL('/en', request.url));
  }
  return Response.next();
}

medium

A. Missing optional chaining on headers.get could cause runtime error

B. Redirect URL is incorrect, should be '/en-US'

C. Response.next() is not a valid method

D. Locale comparison should use locale.includes('en')

Solution

1. Step 1: Check headers.get usage

   headers.get('accept-language') can return null if header missing, so calling split() without check causes error.

2. Step 2: Identify fix

   Using optional chaining like headers.get('accept-language')?.split(',')[0] prevents runtime error.

3. Final Answer:

   Missing optional chaining on headers.get could cause runtime error -> Option A

4. Quick Check:

   Null header needs optional chaining [OK]

Hint: Always check headers.get may return null [OK]

Common Mistakes:

• Assuming headers.get always returns string
• Incorrect redirect URL format
• Using invalid Response methods

5. You want to detect user locale in Next.js by checking cookie first, then header, and fallback to default 'en'. Which code snippet correctly implements this logic in middleware?

hard

A. const locale = 'en' || request.cookies.get('NEXT_LOCALE') || request.headers.get('accept-language');

B. const locale = request.headers.get('accept-language')?.split(',')[0].split('-')[0] || request.cookies.get('NEXT_LOCALE') || 'en';

C. const locale = request.cookies.get('NEXT_LOCALE') || request.headers.get('accept-language')?.split(',')[0].split('-')[0] || 'en';

D. const locale = request.cookies.get('NEXT_LOCALE') && request.headers.get('accept-language') || 'en';

Solution

1. Step 1: Understand priority order

   We want to check cookie first, then header, then default 'en'.

2. Step 2: Analyze each option

   const locale = request.cookies.get('NEXT_LOCALE') || request.headers.get('accept-language')?.split(',')[0].split('-')[0] || 'en'; checks cookie first, then header with safe optional chaining, then 'en'. Others have wrong order or logic.

3. Final Answer:

   const locale = request.cookies.get('NEXT_LOCALE') || request.headers.get('accept-language')?.split(',')[0].split('-')[0] || 'en'; -> Option C

4. Quick Check:

   Cookie first, then header, then default [OK]

Hint: Use || in order: cookie, header, default [OK]

Common Mistakes:

• Checking header before cookie
• Using && instead of || causing wrong logic
• Missing optional chaining on header