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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@papit/translator

v0.1.1

Published

Translation store for papit components and apps. Register languages inline or by URL, fetch them lazily on first use, and translate keys with variable interpolation. Components re-render when the language changes.

Readme

@papit/translator

Translation store for papit components and apps. Register languages inline or by URL, fetch them lazily on first use, and translate keys with variable interpolation. Components re-render when the language changes.

Logo


Type Tests NPM version


Installation

npm install @papit/translator

Usage

import { translator, useTranslator } from "@papit/translator";

translator.add({ id: "en", translations: { greeting: "Hello {name}" } });
translator.add({ id: "sv", url: "/translations/sv.json" }); // fetched on first change

await translator.change("en");

const t = useTranslator();
t("greeting", { name: "Ada" }); // "Hello Ada"
t("missing.key");               // "missing.key"

Nested keys and scopes

Translation files can nest objects; dots in a key walk into them. A scope prefixes every key:

{ "pap-sidebar": { "toggle": "Toggle sidebar" } }
const t = useTranslator("pap-sidebar");
t("toggle"); // "Toggle sidebar"

In a component

import { CustomElement, html } from "@papit/web-component";
import { translate, useTranslator } from "@papit/translator";

class MyElement extends CustomElement {
    @translate t = useTranslator("my-element");

    render() {
        return html`<button>${this.t("close")}</button>`;
    }
}

Entry points

| Import | For | | ------ | --- | | @papit/translator | Browser (same as /browser) | | @papit/translator/browser | Browser, includes the @translate decorator | | @papit/translator/node | Node. No decorator, and useTranslator returns { translate, t } |


API

translator

const translator: {
    add(entry: LanguageJson): void;
    change(entry: string | LanguageJson): Promise<LanguageJson | null>;
    subscribe(fn: () => void): () => void;
    list(): LanguageJson[];
    current(): LanguageJson | null;
    locale(): string | null;
}

The shared store. list, current and locale are @papit/signals readers, so reading them in an effect tracks them.

| Member | Description | | ------ | ----------- | | add(entry) | Registers a language. Ignored if the id is already registered | | change(entry) | Makes a language current, by id or entry. Fetches its url the first time. Resolves null if the id is unknown or the fetch fails | | subscribe(fn) | Calls fn on every later change of language. Returns an unsubscribe function | | list() | Registered languages | | current() | The current language, or null | | locale() | meta.language of the current language, or null |

useTranslator

function useTranslator(scope?: string): (key: string, variables?: Record<string, unknown>) => string

Returns a translate function that always uses the current language.

  • A missing key, or no current language, returns the key.
  • {name} is replaced by variables.name. Unknown placeholders are left as they are.
  • Variable values: strings, numbers, booleans and bigints as text; dates as ISO strings; arrays joined with commas; functions are called; other objects as JSON.

translate

@translate
@translate({ update?: (this: Element) => void })

Browser only. A field decorator for components: subscribes on connectedCallback, unsubscribes on disconnectedCallback, and calls requestUpdate() on each language change. update also runs on each change, and on connect when a language is already set.

Types

type LanguageJson = {
    id: string;
    meta?: { language: string; region: string };
    url?: string;                           // fetched on first change
    translations?: Record<string, unknown>; // required when there's no url
}

Simplified: the declared type of translations is Record<string, string>, though nested objects work at runtime. meta can also sit inside the translations object or JSON file. The translate function's type is exported as TransalatorFn.


License

Licensed under the @Papit License 1.0 Copyright (c) 2024 Henry Pap (@onkelhoy)

Key points

  • ✅ Free to use in commercial projects
  • ✅ Free to modify and distribute
  • ✅ Attribution required
  • ❌ Cannot resell the component itself as a standalone product

See the LICENSE file for full details.


Related Components