Next.js 15 Fullstack (App Router + Server Actions) · 课时

按区域设置格式化日期、数字与复数

使用 Intl 接口渲染符合区域设置的日期、货币和复数形式的字符串。

第 4 / 4 课13 个步骤

按区域设置格式化日期、数字与复数 是 CoddyKit 上的免费 Next.js 15 Fullstack (App Router + Server Actions) 课时。这是第 4 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Next.js 15 Fullstack (App Router + Server Actions) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Next.js 15 Fullstack (App Router + Server Actions) 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Why Locale-Aware Formatting Matters

A date like 06/07/2025 means June 7th to an American, but July 6th to a European. A number like 1.234 is one thousand two hundred thirty-four in the US, but one point two three four in Germany.

Hard-coding format logic breaks your app for international users. Instead, the browser and Node.js both ship the Intl namespace — a standards-based set of APIs that handle locale-aware formatting with zero third-party libraries.

Intl.DateTimeFormat — formats dates and times
Intl.NumberFormat — formats numbers, currencies, and units
Intl.PluralRules — selects the correct plural form

In a Next.js 15 App Router project these run on the server (in Server Components and Server Actions) as well as on the client, so you get consistent output without shipping extra JavaScript.

Detecting the Active Locale in App Router

Next.js 15 with the App Router stores the active locale in the URL segment. A common convention is /en/dashboard or /de/dashboard. Your layout.tsx receives a params prop that contains it.

The snippet below shows how to read params.locale in an async Server Component and pass it down to formatting helpers.

// app/[locale]/layout.tsx
import { ReactNode } from 'react';

interface Props {
  children: ReactNode;
  params: Promise<{ locale: string }>;
}

export default async function LocaleLayout({ children, params }: Props) {
  const { locale } = await params; // e.g. 'en', 'de', 'tr'

  return (
    <html lang={locale}>
      <body>{children}</body>
    </html>
  );
}

Formatting Dates with Intl.DateTimeFormat

Intl.DateTimeFormat accepts a locale string and an options object. You can control which date/time parts to show and in what style.

dateStyle: 'short', 'medium', 'long', 'full'
timeStyle: same options
Individual fields: year, month, day, hour, minute, etc.

Calling .format(date) returns a locale-correct string. Because Intl is built into Node.js, this runs safely inside a Server Component with no client bundle cost.

// lib/format-date.ts
export function formatDate(
  date: Date,
  locale: string,
  options: Intl.DateTimeFormatOptions = { dateStyle: 'long' }
): string {
  return new Intl.DateTimeFormat(locale, options).format(date);
}

// Usage examples:
// formatDate(new Date(), 'en-US') => 'June 7, 2025'
// formatDate(new Date(), 'de-DE') => '7. Juni 2025'
// formatDate(new Date(), 'tr-TR') => '7 Haziran 2025'
// formatDate(new Date(), 'ja-JP') => '2025年6月7日'

Using formatDate in a Server Component

Because Server Components run on Node.js, you can call your formatDate helper directly — no useEffect, no hydration mismatch, no extra bundle weight for the client.

The locale comes from params and is passed straight into the formatter. The result is a plain string embedded in HTML.

// app/[locale]/blog/[slug]/page.tsx
import { formatDate } from '@/lib/format-date';

interface Props {
  params: Promise<{ locale: string; slug: string }>;
}

export default async function BlogPost({ params }: Props) {
  const { locale, slug } = await params;

  // In a real app you would fetch the post from a DB or CMS
  const publishedAt = new Date('2025-06-07T09:00:00Z');

  return (
    <article>
      <time dateTime={publishedAt.toISOString()}>
        {formatDate(publishedAt, locale, { dateStyle: 'full', timeStyle: 'short' })}
      </time>
      <h1>Post: {slug}</h1>
    </article>
  );
}

Formatting Numbers and Currencies

Intl.NumberFormat handles three main use-cases:

Plain numbers — decimal separators and grouping differ by locale (1,234.56 vs 1.234,56)
Currency — symbol placement, decimal precision, and even currency name differ
Units — kilograms, miles, bytes, etc., formatted according to locale conventions

Always pass currency together with style: 'currency'. The currency code (ISO 4217) tells the formatter which symbol to use; the locale tells it where to put it.

// lib/format-number.ts
export function formatCurrency(
  amount: number,
  currency: string,
  locale: string
): string {
  return new Intl.NumberFormat(locale, {
    style: 'currency',
    currency,
    minimumFractionDigits: 2,
    maximumFractionDigits: 2,
  }).format(amount);
}

export function formatNumber(
  value: number,
  locale: string,
  options?: Intl.NumberFormatOptions
): string {
  return new Intl.NumberFormat(locale, options).format(value);
}

// formatCurrency(1234.5, 'USD', 'en-US') => '$1,234.50'
// formatCurrency(1234.5, 'EUR', 'de-DE') => '1.234,50 €'
// formatCurrency(1234.5, 'TRY', 'tr-TR') => '₺1.234,50'

A Standalone Intl Demo (Runnable)

The snippet below is a complete, self-contained TypeScript program that demonstrates Intl.DateTimeFormat and Intl.NumberFormat across several locales. No framework or external package is needed — you can run it with ts-node or paste it into a TypeScript playground.

const locales = ['en-US', 'de-DE', 'tr-TR', 'ja-JP', 'ar-SA'];
const date = new Date('2025-06-07T14:30:00Z');
const price = 9999.99;

for (const locale of locales) {
  const formattedDate = new Intl.DateTimeFormat(locale, {
    dateStyle: 'medium',
    timeStyle: 'short',
  }).format(date);

  const formattedPrice = new Intl.NumberFormat(locale, {
    style: 'currency',
    currency: 'USD',
  }).format(price);

  console.log(`[${locale}]  date: ${formattedDate}  |  price: ${formattedPrice}`);
}

Plural Rules — the Hidden Complexity

English has two plural forms: 1 item vs 2 items. But Arabic has six, Russian has three, and Polish has four. If you build pluralization with a simple count === 1 ? 'item' : 'items' check, your app will be wrong for most of the world.

Intl.PluralRules solves this by returning the correct CLDR plural category for a given number and locale:

zero
one
two
few
many
other

You map each category to the correct translated string in your message catalog, then let PluralRules pick the right key at runtime.

Implementing a pluralize Helper

The helper below accepts a count, a locale, and a map of plural category strings. It uses Intl.PluralRules to select the right form, then replaces a {{count}} placeholder with the actual number.

This keeps plural logic out of your translation files — the files only need the per-category templates, not branching code.

// lib/pluralize.ts
type PluralForms = Partial<Record<Intl.LDMLPluralRule, string>>;

export function pluralize(
  count: number,
  locale: string,
  forms: PluralForms
): string {
  const rules = new Intl.PluralRules(locale);
  const category = rules.select(count); // 'zero'|'one'|'two'|'few'|'many'|'other'
  const template = forms[category] ?? forms['other'] ?? '';
  return template.replace('{{count}}', String(count));
}

// English
// pluralize(1, 'en', { one: '{{count}} item', other: '{{count}} items' })
// => '1 item'

// pluralize(5, 'en', { one: '{{count}} item', other: '{{count}} items' })
// => '5 items'

// Arabic (6 forms)
// pluralize(11, 'ar', { zero:'...', one:'...', two:'...', few:'...', many:'{{count}} عنصرًا', other:'...' })
// => '11 عنصرًا'

Using pluralize in a Server Component

Combine the pluralize helper with locale-aware number formatting for a complete, production-ready solution. The cart summary below shows item count and total price, both correctly formatted for any locale.

// app/[locale]/cart/page.tsx
import { pluralize } from '@/lib/pluralize';
import { formatCurrency } from '@/lib/format-number';

interface Props {
  params: Promise<{ locale: string }>;
}

// Minimal translation catalog — in real projects use next-intl or similar
const itemForms: Record<string, Record<string, string>> = {
  'en-US': { one: '{{count}} item',     other: '{{count}} items' },
  'de-DE': { one: '{{count}} Artikel',  other: '{{count}} Artikel' },
  'tr-TR': { one: '{{count}} ürün',     other: '{{count}} ürün' },
};

export default async function CartPage({ params }: Props) {
  const { locale } = await params;
  const itemCount = 3;
  const total = 129.99;
  const forms = itemForms[locale] ?? itemForms['en-US'];

  return (
    <section>
      <p>{pluralize(itemCount, locale, forms)}</p>
      <p>Total: {formatCurrency(total, 'USD', locale)}</p>
    </section>
  );
}

Relative Time Formatting with Intl.RelativeTimeFormat

Intl.RelativeTimeFormat formats durations relative to now — 3 days ago, in 2 hours — in any locale and any numeric style.

numeric: 'always' — always uses numbers: 1 day ago
numeric: 'auto' — uses natural language when possible: yesterday

The helper below computes the best unit automatically and delegates the string to the API.

// lib/format-relative.ts
export function formatRelative(date: Date, locale: string): string {
  const rtf = new Intl.RelativeTimeFormat(locale, { numeric: 'auto' });
  const diffMs = date.getTime() - Date.now();
  const diffSec = Math.round(diffMs / 1000);

  const thresholds: [number, Intl.RelativeTimeFormatUnit][] = [
    [60, 'second'],
    [3600, 'minute'],
    [86400, 'hour'],
    [2592000, 'day'],
    [31536000, 'month'],
  ];

  for (const [limit, unit] of thresholds) {
    if (Math.abs(diffSec) < limit) {
      const divisor = unit === 'second' ? 1
        : unit === 'minute' ? 60
        : unit === 'hour' ? 3600
        : unit === 'day' ? 86400
        : 2592000;
      return rtf.format(Math.round(diffSec / divisor), unit);
    }
  }

  return rtf.format(Math.round(diffSec / 31536000), 'year');
}

// formatRelative(new Date(Date.now() - 90000), 'en-US') => '2 minutes ago'
// formatRelative(new Date(Date.now() - 90000), 'de-DE') => 'vor 2 Minuten'

Creating a Reusable FormattedDate Client Component

Sometimes you need date formatting on the client — for example, when the date changes after user interaction. A thin Client Component that reads navigator.language avoids hydration mismatches by letting the browser pick its own locale.

Notice the 'use client' directive. The component itself ships no Intl polyfill because all modern browsers and Node 18+ support the full Intl spec natively.

'use client';

import { useMemo } from 'react';

interface Props {
  date: string; // ISO string — safe to serialize from Server to Client
  options?: Intl.DateTimeFormatOptions;
}

export function FormattedDate({ date, options = { dateStyle: 'medium' } }: Props) {
  // navigator.language gives the browser's locale, e.g. 'en-GB'
  const formatted = useMemo(() => {
    return new Intl.DateTimeFormat(navigator.language, options).format(
      new Date(date)
    );
  }, [date, options]);

  return <time dateTime={date}>{formatted}</time>;
}

Knowledge Check: Plural Forms and Intl.PluralRules

Based on what you learned in this lesson, answer the following question about Intl.PluralRules and locale-aware pluralization.

在交互式课程中回答

Recap: Locale-Aware Formatting in Next.js 15

In this lesson you learned how to use the built-in Intl APIs to format dates, numbers, currencies, relative times, and pluralized strings correctly for any locale — with no third-party libraries required.

Intl.DateTimeFormat — formats dates and times; use dateStyle/timeStyle for quick output or individual field options for fine control.
Intl.NumberFormat — handles plain numbers, currencies (style: 'currency'), and units; always pair a currency code with the locale.
Intl.RelativeTimeFormat — produces locale-correct relative strings like yesterday or vor 2 Minuten.
Intl.PluralRules — selects the CLDR plural category (zero / one / two / few / many / other) so your translation catalog can provide the right form for every language.
In Next.js 15 App Router, run these formatters in Server Components to avoid hydration mismatches and bundle cost; use a 'use client' wrapper with navigator.language only when client-side locale detection is needed.

These four Intl APIs cover the vast majority of i18n formatting needs without reaching for a heavy library.

免费开始

用 AI 导师学习 TypeScript — 免费

在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。

课程: 22
课程: 88

免费开始学习查看完整课程

常见问题解答

「按区域设置格式化日期、数字与复数」课时是免费的吗？

是的 — 「按区域设置格式化日期、数字与复数」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Next.js 15 Fullstack (App Router + Server Actions) 课程的其余内容，请升级到 CoddyKit PRO。 Next.js 15 Fullstack (App Router + Server Actions) 课程共包含 4 节课。

「按区域设置格式化日期、数字与复数」这节课中我会学到什么？

使用 Intl 接口渲染符合区域设置的日期、货币和复数形式的字符串。你通过在浏览器中直接运行的动手代码来练习 Next.js 15 Fullstack (App Router + Server Actions)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Next.js 15 Fullstack (App Router + Server Actions) 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Next.js 15 Fullstack (App Router + Server Actions) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 4 节课，共 4 节。

「按区域设置格式化日期、数字与复数」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Next.js 15 Fullstack (App Router + Server Actions) 课中编写并运行代码吗？

能。每节 Next.js 15 Fullstack (App Router + Server Actions) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Next.js 15 Fullstack (App Router + Server Actions)