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

@prepair/locale-support

v2.2.3

Published

Locale related data for prepair in a bundle.

Downloads

211

Readme

locale-support

Locale related data in a neat bundle.

Warning: locale and currency connections are defined by @prepair specs (meaning that even though in a country the standard currency may be XXX, we support payments in YYY so we will use the latter in the config file).

supported locales

supportedLocales = ["ar-ae","bg-BG","bs-Latn-BA","ca-ES","cs-CZ","de-DE","el-GR","en-GB","es-ES","fr-FR","he-IL","hi-IN","hu-HU","it-IT","ka-GE","lt-LT","lv-LV","mk-MK","nb-NO","nl-NL","pl-PL","pt-PT","ro-RO","ru-RU","sk-SK","sq-AL","sr-Cyrl-CS","sv-SE","uk-UA","zh-CN"];

installation

npm i -S @prepair/locale-support
  • metadata code generator assumes a node context.
  • use metadata in the browser with webpack or browserify.
  • use generated code in your own repository.

usage

metadata

import { metadata } from '@prepair/locale-support';
  • contains locale data for accounting
  • contains currency data (code, short symbol, precision)

mod rewrite partial regexp

Returns a regexpish partial string for mod rewrite, created from the dotnet lang ids.

For example: bg-bg|bs-latn-ba|cs-cz

const localeSupport = require('@prepair/locale-support');
const ruleChunk = localeSupport.getModRewriteRex();
  • with no params it returns all the lang ids
  • ids are sorted before concatenation
  • localeSupport.getModRewriteRex({rtl: true}) - rtl only ids
  • localeSupport.getModRewriteRex({rtl: false}) - non rtl only ids

adding new locales

Add new data to ./src/config.js

  • .NET locale id (see: http://www.localeplanet.com/)
  • currency preferred by @prepair
  • cldr id

then run npm run build.

TODO

  • refactor "src - lib - lib-es5" so that instead of 2 build cycles we should use 1
  • transpile config.js, before someone accidentally adds an es6 keyword there