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

@shore/i18n

v1.2.0

Published

A wrapper around some *i18next* functionality - encapsulating *namespaced* translations.

Downloads

54

Readme

i18n

A wrapper around some i18next functionality - encapsulating namespaced translations.

Usage

Translation file ./de/translation.json:

{
  "english": "Englisch"
}

Translation file ./de/my-namespace.json:

{
  "Hello world!": "Hallo Welt!"
}

Application example:

import i18n from '@shore/i18n';

i18n.init({
  locale: 'de',
  ...
})
.then(() => {
  console.log(i18n.locale); // -> 'de'
  console.log(i18n.t('english')); // -> 'Englisch'

  return i18n.loadNamespace('my-namespace');
})
.then((i18nNamespaced) => {
  console.log(i18nNamespaced.t('Hello world!')); // -> 'Hallo Welt!'
});

If i18next should not be bundled because the embedding page already made it globally available through window.i18n and called init on it, use:

import i18n from '@shore/i18n/no-bundled-i18next';

console.log(i18n.locale); // -> 'de'
i18n.loadNamespace('my-namespace')
.then((i18nNamespaced) => {
  console.log(i18nNamespaced.t('Hello world!')); // -> 'Hallo Welt!'
});

If you want to conveniently use namespaced version of t and exists across modules:

// i18n.js
import i18n from '@shore/i18n/no-bundled-i18next';

const namespace = 'my-namespace';

export default i18n;
export function loadDefaultNamespace() {
  return i18n.loadNamespace(namespace);
}
export const i18nNamespaced = i18n.useNamespace(namespace);


// my-module.js
import { i18nNamespaced as i18n } from './i18n';

export function helloWorld() {
  return i18n.t('Hello World!');
}


// main.js
import { loadDefaultNamespace } from './i18n';
import { helloWorld } from './my-module';

loadDefaultNamespace().then(() => {
  console.log(helloWorld()); // -> 'Hallo Welt!'
});