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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@tradeshift/g11n-langneg

v1.3.2

Published

Language negotiation for the masses

Downloads

985

Readme

g11n-langneg

Language negotiation helpers

Usage

import { Locale, match } from "@tradeshift/g11n-langneg";

const result: Locale = match("pt-Latn-BR", ["da", "en", "es", "pt"]);
// result == Locale.parse('pt')`

// also accepts `Locale` objects as inputs
const result2: Locale = match(Locale.parse("pt-Latn-BR"), [
  Locale.parse("da"),
  Locale.parse("pt"),
]);
// result2 == Locale.parse('pt')`

If there's no match, it will return the first candidate in the list, so the first element should always be your preferred/default locale.

const result: Locale = match("pt", ["en", "da", "es"]);
// result == Locale.parse('en')`

Locale

Parsing (strict and lenient)

import { Locale } from "@tradeshift/g11n-langneg";

// lenient parsing of locales, invalid locales will parse to `und`
const locale: Locale = Locale.parse("pt-BR");

// strict parsing of locales will throw errors for invalid locales
try {
  const invalid = Locale.parseStrict("abcdefghijklmnopq");
} catch (e) {
  throw e;
}

Maximization (Likely Subtags)

Note: g11n-langneg uses a small subset of the likely subtags CLDR data

const locale: Locale = Locale.parse("pt-BR");
const maximized: Locale = locale.maximize(); // equivalent to 'pt-Latn-BR'

Accessing and modifying subtags

const locale: Locale = Locale.parse("pt-Latn-BR");

const language: string = locale.getLanguage(); // pt
const script: string = locale.getScript(); // Latn
const region: string = locale.getRegion(); // BR

const ptCyrl: Locale = locale.setScript("Cyrl"); // pt-Cyrl-BR
const ptPT: Locale = locale.setRegion("PT"); // pt-Latn-PT

Release

Semantic release: (Commit conventions)

No new version will be released unless specific commit message is used. See Commit conventions for details. If a release is expected, please fix commit messages to align with appropriate format