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

@spryker/locale

v2.0.7

Published

## I18N

Downloads

20,850

Readme

locale

I18N

Any package may have it's own set of localization data.

Locale package will locate all such data by the following glob: libs/*/src/i18n/*.ts.

The file name must match the targeted locale name specified as folders in locales/*.

The file must export default interface called I18nLocaleDataPackage.

The name in each locale file must be specified and will be used to prefix all tokens with it via dot (.) - so later translations must reference it with this name prefixed. This is done for easier navigation of the source of translations.

For example:

  • If the file specifies that name is prefix
  • And if the file defined translation with token example
  • Then in the application to get this translation use token prefix.example

Bundling

Before the build phase all such locale files will be found in all packages and aggregated in single data files by a target language which later will be included in the specific locale NgModule via lazy-loading.


This library was generated with Nx.

Running unit tests

Run nx test locale to execute the unit tests.