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

localtor

v1.0.3

Published

JavaScript lib for detecting user's locale by varoius sources (cookies, HTTP, URL, etc.).

Downloads

2

Readme

localtor

JavaScript lib for detecting user's locale by varoius sources (cookies, HTTP, URL, etc.). It does not offer any cookie parser or geo library, it does rather offer a way to combine all data sources, filter out invalid data and to get the best match. It does accept various inputs and it filters invalid data out. Just specify the allowed locals.

Version Downloads Dependencies Size gzipped Size minified

Installation

yarn add localtor

npm i localtor -S

Basic Usage

  import localtor from 'localtor';
  
  let locale = '';
  
  locale = localtor({
    locales: ['en', 'de-CH', 'ru-RU', 'fr'],
  }).getLocale([
    'ru',
    'de-CH',
    'en-GB,en;q=0.8,sv',
  ]);
  console.log(locale); //results in 'ru-RU'
  
  locale = localtor({
    locales: ['en', 'de-CH', 'ru-RU', 'fr'],
  }).getLocale([
    false,
    'it-IT',
    ['ar', 'hr'],
    'en-GB,en;q=0.8,sv',
  ]);
  console.log(locale); //results in 'en'

The order is important. The first valid element in the array will be returned. It ignores everything except the defined locales. If you don't define any default locale, then the first entry from options.locales is used as the default value.

Advanced Usage

  import localtor from 'localtor';
  
  let locale = '';

  //get
  locale = localtor({
    default: 'fr',
    locales: ['en', 'de-CH', 'ru-RU', 'fr'],
  }).get([
    ['ru'],
    'de-CH',
    'fr',
  ]);
  console.log(locale);
  /* results in:
  {
    match: 'ru-RU',
    matches: [
      'ru-RU',
      'de-CH',
      'fr',
    ],
  }
  */
  
  //getLocales
  locale = localtor({
    default: 'fr',
    locales: ['en', 'de-CH', 'ru-RU', 'fr'],
  }).getLocales([
    ['ru'],
    'de-CH',
    'fr',
  ]);
  console.log(locale);
  /* results in:
  [
    'ru-RU',
    'de-CH',
    'fr',
  ]
  */
  
  //It's also possible to pass 'named' elements; the names will be preserved and the result
  //would be a normal object instead of an array.
  locale = localtor({
    default: 'fr',
    locales: ['en', 'de-CH', 'ru-RU', 'fr'],
  }).getLocales([
    {pathname: 'ru'},
    {cookie: 'de-CH'},
    {http: 'fr-FR,en;q=0.8,sv'},
  ]);
  console.log(locale);
  /* results in:
  {
    pathname: 'ru-RU',
    cookie: 'de-CH',
    http: 'fr',
  }
  */

Why?

Maximum freedom, easy to use, works well with server-side-rendering (same result). Some real usage example:

server.js:

  const locales = localtor({
    default: config.i18n.default,
    locales: config.i18n.locales,
  }).get([
    {pathname: req.originalUrl.substr(1,5)},
    {cookie: req.cookies.locale},
    {http: req.headers["accept-language"] },
  ]);

Could result in: { match: 'de-CH', matches: { pathname: null, cookie: null, http: 'de-CH' } }

client.js:

  const locale = localtor({
    default: config.i18n.default,
    locales: config.i18n.locales,
  }).getLocale([
    window.location.pathname.substr(1,5),
    Cookies.get('locale'),
  ]);

Could result in: de-CH