npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@shotlingo/locale-fallback

v0.1.0

Published

Resolve any BCP-47 locale tag to the nearest one App Store Connect or Google Play Console actually supports, with the full fallback chain. Zero dependencies, no network calls.

Readme

@shotlingo/locale-fallback

Resolve any BCP-47 locale tag to the nearest one App Store Connect or Google Play Console actually supports, with the full fallback chain. Zero dependencies, no network calls.

Locale ↔ locale code mapping (no fallback logic): @shotlingo/locale-codes Full interactive reference: shotlingo.com/tools/app-store-locale-codes

Why this matters

A device or OS can report a locale neither store lists as a metadata locale — es-AR, en-NZ, pt-AO, or Google Play's own legacy subtags iw/in for Hebrew/Indonesian. Upload that tag as-is, or key a screenshot set on it directly, and you get nothing: no listing locale, no matching localized asset. This resolves it to a locale the store will actually accept, and exposes the chain it fell back through so you can log or test what happened instead of guessing.

Install

npm install @shotlingo/locale-fallback

Usage

import { resolveLocale, fallbackChain, supportedLocales, isSupportedLocale } from '@shotlingo/locale-fallback';

resolveLocale('en-NZ', 'appStore');
// => 'en-US' (not a listing locale; falls back to base language)

resolveLocale('iw-IL', 'appStore');
// => 'he' (Play's own legacy Hebrew subtag, normalized before matching)

resolveLocale('zh-Hant-HK', 'appStore');
// => 'zh-Hant' (language+script truncation, not the first zh-* entry)

fallbackChain('es-AR', 'appStore');
// => ['es-ES', 'en-US'] — what it tried, in order

isSupportedLocale('en-NZ', 'appStore');
// => false — exact match only, no fallback applied

supportedLocales('play').length;
// => 40

API

  • resolveLocale(requested: string, store: 'appStore' | 'play'): string — the single best-matching locale code.
  • fallbackChain(requested: string, store): string[] — every code tried, in order, deduplicated. [0] is what resolveLocale returns.
  • supportedLocales(store): string[] — every locale code this table lists for that store.
  • isSupportedLocale(requested: string, store): boolean — exact match only (case-insensitive), no fallback.
  • LOCALES: LocaleEntry[] — the underlying 40-language table ({ language, appStoreCode, googlePlayCode }).
  • DEFAULT_LOCALE: Record<Store, string>{ appStore: 'en-US', play: 'en-US' }, the last resort in every chain.

Lookup order: exact match on the tag as given → exact match after normalizing legacy subtags (iwhe, inid) → the normalized tag truncated to language+script/region → base language only → the store default. This is a language-level lookup, not a full RFC 4647 algorithm with script/region weighting — for the 40 languages this table covers, that's the difference that actually changes which screenshot set or listing locale gets picked.

License

MIT