OrdinalText
SM · 950B gzip budgetAn ordinal via Intl.PluralRules — correct at 11th, and silent where suffixes do not apply.
- Category
- Internationalisation
- Budget
- sm, single-purpose control
- External runtime
- React / React DOM only
axe fixtureSSR rendersource scanbundle budget
Preview
Live fixture23rd
Try the component here. Locale-aware formatting and direction follow the selected language; example content and labels are not automatically translated. Overlay demos use interactive launchers.
Why this exists
OrdinalText
EnglishThe st/nd/rd/th rule breaks at 11, 12 and 13, and does not apply at all in languages that do not build ordinals from suffixes.
Formatting shortcut
11st · 12nd · 13rd · 21st
n % 10 === 1 ? `${n}st` : …Install
npx shadcn@latest add https://gear5-ui.vercel.app/r/ordinal-text.jsonCopies the source into your project. Pulls in 2 shared registry items: use-locale, locale.
New here? Set up Tailwind and import aliases first →Source & props
Edit on GitHub ↗Prop types and inline documentation are included below. This is repository source; the installer rewrites shared imports for your project.
"use client";
import { useMemo } from "react";
import { useLocale } from "../lib/use-locale";
export interface OrdinalTextProps {
value: number;
/**
* Suffixes keyed by CLDR ordinal category. Only needed for locales whose
* ordinals are suffix-based, like English's st/nd/rd/th. Locales that form
* ordinals differently fall back to the plain number, which is correct —
* appending "th" to a Japanese numeral is worse than appending nothing.
*/
suffixes?: Partial<Record<Intl.LDMLPluralRule, string>>;
}
const ENGLISH_SUFFIXES: Partial<Record<Intl.LDMLPluralRule, string>> = {
one: "st",
two: "nd",
few: "rd",
other: "th",
};
/*
* Rendered inside a `suppressHydrationWarning` span.
*
* `Intl` output is not byte-identical across ICU versions, and Node's ICU is
* not the browser's. This exact call produces "Jan 1 <U+2009>–<U+2009> 5, 2026"
* on Node and "Jan 1 <U+0020>–<U+0020> 5, 2026" in Chrome — visually
* identical, different bytes — so every server-rendered use would throw a
* hydration error in a consumer's app through no fault of theirs.
*
* This is the case React documents the escape hatch for. The suppression is
* scoped to this one text node, so a genuine structural mismatch anywhere else
* still reports normally.
*/
/**
* An ordinal — 1st, 2nd, 3rd — using `Intl.PluralRules` in ordinal mode.
*
* The rule is not "1 → st, 2 → nd, 3 → rd, everything else → th": 11th, 12th
* and 13th break it, and so does every locale that does not build ordinals by
* suffix at all. `Intl.PluralRules` knows both.
*/
export function OrdinalText({ value, suffixes }: OrdinalTextProps) {
const { locale } = useLocale();
const text = useMemo(() => {
const number = new Intl.NumberFormat(locale).format(value);
const table = suffixes ?? (locale.startsWith("en") ? ENGLISH_SUFFIXES : undefined);
if (!table) return number;
const category = new Intl.PluralRules(locale, { type: "ordinal" }).select(value);
return `${number}${table[category] ?? ""}`;
}, [locale, value, suffixes]);
return <span suppressHydrationWarning>{text}</span>;
}
What CI checks
Quality contract- Bundled, minified and gzipped against its tier budget
- Audited by axe in the state previewed above
- Rendered through react-dom/server with no browser globals
- Scanned for network calls, dangerous sinks, and unguarded animation