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

@oliversalzburg/lit-i18n

v4.0.1

Published

lit-element based i18n solution backed by i18next

Downloads

9

Readme

@oliversalzburg/lit-i18n

Forked from https://github.com/colscott/lit-i18n, as that package seems to be no longer maintained.

i18next lit-html directive (could possible add other i18n backends).

Install

yarn add @oliversalzburg/lit-i18n

Usage

Config

Nothing new here. Just use the usual i18next config. You can import from i18next.

i18next.init({
    lng: "en",
    resources: {
        en: {
            translation: {
                whatishow: "{{what}} is {{how}}",
                datamodel:
                    "{{person.name}} is a {{person.age}} year old and is male: {{person.male}}",
            },
        },
        fr: {
            translation: {
                whatishow: "{{what}} est {{how}}",
                datamodel: "{{person.name}} a {{person.age}} ans et est un homme: {{person.male}}",
            },
        },
    },
});

Translations

lit-i18n exposes two directives called translate and translateWhen. The translate directive has the same signature and functionality as the i18next t method. lit-i18n also exposes lit-htmls html and render methods.

translate

import { translate as t, html, render } from "@oliversalzburg/lit-i18n/lib/lit-i18n.js";

/** @typedef {{name: string; age: number; male: boolean}} Person */
class I18nElement extends HTMLElement {
    /** @returns {Person} */
    get person() {
        return this._person;
    }

    /** @param {Person} */
    set person(value) {
        this._person = value;
        render(this.renderTemplate, this);
    }

    /** @inheritdoc */
    constructor() {
        super();
    }

    /** @inheritdoc */
    connectedCallback() {
        if (!this.person) {
            this.person = {
                name: "None",
                age: 0,
                male: false,
            };
        }
    }

    /** @returns {import('lit-html/lit-html').TemplateResult} */
    get renderTemplate() {
        return html`
            <div title="${t("whatishow", { what: "i18next", how: "great" })}"></div>
            <span>${t("datamodel", { person: this.person })}</span>
        `;
    }
}

translateWhen directive - postponing translations until they have loaded

Screen flicker can occur if you load multiple namespaces and run translations prior to the translation resource being loaded. I18next returns promises that will resolve after the resources are ready. If this happens you can use translateWhen. translateWhen differs to translate in that it also accepts a Promise. This Promise would typically be the Promise returned by i18next.init or i18next.loadNamespaces or i18next.loadLanguages. The translateWhen directive will not try to translate the key until the Promise is resolved. Passing the Promise every single time you call the directive can get a little much so you can wrap the directive and call the wrapper instead, like this:

import { translateWhen } from '@oliversalzburg/lit-i18n/lib/lit-i18n.js';

const initializePromise = i18next.use(someBackend).init(....);
const translateDirective = (keys, options) => translateWhen(initializePromise, keys, options);

// Now you can use translateDirective in your lit-html templates.
html`<div>${translateDirective('some.key')}</div>`