Locale detection strategies in NextJS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does Next.js detect locale using the Accept-Language header?

In Next.js, when using internationalized routing, how does the framework use the Accept-Language HTTP header to detect the user's locale?

A Next.js ignores the <code>Accept-Language</code> header and always defaults to the first locale in the configuration.

B Next.js requires manual parsing of the <code>Accept-Language</code> header in a custom middleware to detect locale.

C Next.js uses the <code>Accept-Language</code> header only on the client side after hydration to update the locale dynamically.

D Next.js reads the <code>Accept-Language</code> header on the server and matches the first supported locale from the header's list to set the locale.

💡 Hint

Think about how Next.js handles locale detection on the server before rendering.

Next.js automatically reads the Accept-Language header on the server side during the initial request. It compares the languages listed in the header with the supported locales configured in next.config.js. The first matching locale is selected for rendering the page.

❓ state_output

intermediate

What locale is set when cookie and Accept-Language conflict?

Consider a Next.js app configured with locales ['en', 'fr']. The user has a cookie NEXT_LOCALE=fr but their browser sends Accept-Language: en-US,en;q=0.9. Which locale will Next.js use for rendering the page?

A Next.js will default to the first locale in the config, <code>en</code>, ignoring both cookie and header.

B The locale from the cookie, <code>fr</code>, is used because cookies have higher priority.

C The locale from the <code>Accept-Language</code> header, <code>en</code>, is used because it reflects the browser preference.

D Next.js will throw an error due to conflicting locale sources.

💡 Hint

Think about how Next.js prioritizes locale sources.

Next.js prioritizes the locale stored in the NEXT_LOCALE cookie over the Accept-Language header. This allows user preferences to persist across sessions.

📝 Syntax

advanced

Identify the correct middleware code for locale detection

Which middleware code snippet correctly detects the locale from the Accept-Language header and redirects to the matching locale path in Next.js 14+?

A

import { NextResponse } from 'next/server';
export function middleware(request) {
  const acceptLang = request.headers.get('accept-language');
  const locale = acceptLang?.split(',')[0].split('-')[0] || 'en';
  return NextResponse.redirect(new URL(`/${locale}`, request.url));
}

B

import { NextResponse } from 'next/server';
export function middleware(request) {
  const locale = request.headers['accept-language'].split(',')[0];
  return NextResponse.redirect(`/${locale}`);
}

C

import { NextResponse } from 'next/server';
export function middleware(request) {
  const locale = request.headers.get('accept-language').split(',')[0];
  return NextResponse.redirect(new URL(`/${locale}`, request.url));
}

D

import { NextResponse } from 'next/server';
export function middleware(request) {
  const acceptLang = request.headers.get('accept-language');
  const locale = acceptLang.split(';')[0];
  return NextResponse.redirect(new URL(`/${locale}`, request.url));
}

💡 Hint

Remember to safely access headers and parse the language code correctly.

Option A correctly uses request.headers.get to access the header, safely handles optional chaining, extracts the primary language code, and constructs a new URL for redirection.

Option A incorrectly accesses headers as an object, which is invalid. Option A misses optional chaining and can cause errors if header is missing. Option A incorrectly splits by semicolon instead of comma.

🔧 Debug

advanced

Why does locale detection fail in this Next.js middleware?

Given this middleware code snippet, why does locale detection fail and always redirect to '/en' regardless of the browser language?

import { NextResponse } from 'next/server';
export function middleware(request) {
  const acceptLang = request.headers.get('accept-language');
  const locale = acceptLang.split(',')[0];
  if (!['en', 'fr'].includes(locale)) {
    return NextResponse.redirect(new URL('/en', request.url));
  }
  return NextResponse.next();
}

A The code does not handle the case when <code>acceptLang</code> is null, causing a runtime error and fallback to '/en'.

B The middleware does not return a response for valid locales, causing Next.js to default to '/en'.

C The locale extracted includes region codes like 'en-US', which do not match 'en' or 'fr' exactly, causing the redirect.

D The <code>includes</code> check is case-sensitive but the locale is always uppercase, causing mismatch.

💡 Hint

Look closely at how the locale string is extracted and compared.

The acceptLang.split(',')[0] returns values like 'en-US' or 'fr-FR'. Since the code checks if this full string is in ['en', 'fr'], it fails and redirects to '/en' every time.

To fix this, the code should extract only the primary language code before the dash.

🧠 Conceptual

expert

What is the best practice for locale detection in Next.js 14+ with App Router?

In Next.js 14+, what is the recommended best practice for detecting and setting the user's locale for internationalized routing?

A Use the built-in Next.js i18n routing with <code>next.config.js</code> locales and rely on automatic detection via <code>Accept-Language</code> header and cookies, combined with middleware for redirects.

B Manually parse the <code>Accept-Language</code> header in every server component and set locale state accordingly without using Next.js i18n config.

C Use client-side JavaScript to detect browser language and then reload the page with the correct locale path.

D Disable Next.js i18n routing and handle all locale detection and routing logic in custom Express.js middleware.

💡 Hint

Think about how Next.js integrates locale detection with routing and middleware.

Next.js encourages using the built-in i18n routing configured in next.config.js. It automatically detects locale from the Accept-Language header and cookies. Middleware can be used to redirect users to the correct locale path seamlessly.

Manual parsing or client-side detection is less efficient and can cause flicker or inconsistent routing.