anyaround API reference

anyaround turns a region, language, script, currency, or calendar code into its localized name — and, for countries, an emoji flag. One function over native Intl.DisplayNames, zero dependencies.

import { anyaround } from "anyaround";

anyaround("US");                        // "United States"
anyaround("US", { display: "flag-name" }); // "🇺🇸 United States"
anyaround("US", { locale: "ru" });      // "Соединенные Штаты"
anyaround("en");                        // "English"
anyaround("Cyrl");                      // "Cyrillic"
anyaround("EUR");                       // "Euro"

npm install anyaround
pnpm add anyaround
yarn add anyaround

Ships ESM + CJS with type declarations. Requires a runtime with Intl.DisplayNames (Node 18+, modern browsers). Or take the whole family at once with npm install anyfamily.

anyaround(code, options?) → string

Resolves a code to a ready-to-render string. In the default smartmode the kind is inferred from the code's shape.

anyaround("FR");                     // "France"
anyaround("fr");                     // "French"
anyaround("419");                    // "Latin America and the Caribbean"
anyaround("Latn");                   // "Latin"
anyaround("JPY");                    // "Japanese Yen"
anyaround("DE", { display: "flag" }); // "🇩🇪"

Throws TypeError on an empty code and RangeError on an unknown mode.

2.0 removed the separate anyaroundInfo— they are the same functions and values, reached through the one name the package exports.

- import { anyaround, anyaroundInfo } from 'anyaround'
+ import { anyaround } from 'anyaround'

- anyaroundInfo('US')
+ anyaround.info('US')

Arguments, return values and throwing behaviour are unchanged, and nothing else in the API moved. Every any* package follows this shape from 2.0 on: the bare call does the job, everything else hangs off the same name.

anyaround.info(code, options?) → { code, type, name, flag, found }

Same arguments, structured result — build your own output or drive a <select>.

anyaround.info("US", { locale: "en" });
// { code: "US", type: "region", name: "United States", flag: "🇺🇸", found: true }

anyaround.info("en", { locale: "fr" });
// { code: "en", type: "language", name: "anglais", flag: "", found: true }

anyaround.info("QZ", { mode: "region" });
// { code: "QZ", type: "region", name: "QZ", flag: "🇶🇿", found: false }

flag is "" whenever the code is not a flag-bearing alpha-2 region. found is false when Intl had no name — name is then the code or "", so you can tell a hit from a miss.

The mode option picks how a code is read. Default is "smart".

smart — auto-detect by shape

three digits            → region    "419"
four letters            → script    "Latn"
two uppercase letters   → region    "US"
three uppercase letters → currency  "USD"
anything else           → language  "en", "zh-Hant"

Case is the tiebreaker: "IT" is a region, "it" a language. Pin ambiguous codes with mode. calendar is never auto-detected.

region / language / script / currency / calendar

anyaround("DE", { mode: "region", display: "flag-name" }); // "🇩🇪 Germany"
anyaround("en-US", { mode: "language" });                 // "American English"
anyaround("Cyrl", { mode: "script" });                    // "Cyrillic"
anyaround("EUR", { mode: "currency" });                   // "Euro"
anyaround("gregory", { mode: "calendar" });               // "Gregorian Calendar"

Flags are derived from a two-letter region code by mapping each letter to its Unicode Regional Indicator Symbol — no image assets, no lookup table.

anyaround("US", { display: "flag" });      // "🇺🇸"
anyaround("US", { display: "flag-name" }); // "🇺🇸 United States"
anyaround("US", { display: "name-flag" }); // "United States 🇺🇸"

Numeric M49 regions ("419") and non-region kinds have no flag, so flag display values fall back to the name.

The options type is a discriminated union on mode — TypeScript only offers display in smart / region mode and languageDisplay in language mode.

Every one of these is a file somebody is maintaining by hand right now.

Copy, paste, move on.

// Country picker with flags
countries.map((cc) => {
  const { code, name, flag } = anyaround.info(cc)
  return <option key={code} value={code}>{flag} {name}</option>
})

// Language switcher, each language in its own tongue
anyaround('de', { mode: 'language', locale: 'de' })   // "Deutsch"
anyaround('ja', { mode: 'language', locale: 'ja' })   // "日本語"

// Profile location
anyaround(user.country, { display: 'flag-name', locale: 'en' })
// "🇩🇪 Germany"

// Currency label next to an amount
anyaround(order.currency, { mode: 'currency', locale: 'en' })
// "Euro"

// Flag only, for a compact table cell
anyaround(row.country, { display: 'flag' })
// "🇺🇸" 

anyaround is pure and synchronous, so it works in a component as-is. Whatanyfamily-react adds is a shared locale: set it once onAnyfamilyProvider and every hook below picks it up, so you do not thread locale through every call.

import { AnyfamilyProvider, useAnyaround } from 'anyfamily-react'

function Country({ code }: { code: string }) {
  return <span>{useAnyaround(code, { display: 'flag-name' })}</span>
}

<AnyfamilyProvider locale="en">
  <Country code={user.country} />
</AnyfamilyProvider>

Pass any valid BCP 47 tag, including regional variants and fallback arrays.

anyaround("US", { locale: "ru" }); // "Соединенные Штаты"
anyaround("US", { locale: "de" }); // "Vereinigte Staaten"
anyaround("US", { locale: "ja" }); // "アメリカ合衆国"
anyaround("US", { locale: ["sr-Latn-RS", "en"] });

Output is pure — no Date.now(), no environment reads — so server and client render identically. SSR-safe by construction.

What you would otherwise reach for, and what changes if you do.

anyaround carries no country data at all — it borrows the ICU tables already in your runtime. Zero payload, with the trade that exact strings track the runtime's ICU version rather than a version you pinned.

Intl.DisplayNames is required (widely available since 2021). CI runs on Node 20, 22, and 24.