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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@sonardigital/translations

v1.1.3

Published

A tiny React/i18next helper that bootstraps i18n, provides a lightweight context, and exposes ergonomic hooks for app-wide translations and namespaced keys.

Readme

@sonardigital/translations

A tiny React/i18next helper that bootstraps i18n, provides a lightweight context, and exposes ergonomic hooks for app-wide translations and namespaced keys.

Installation

npm install @sonardigital/translations i18next react-i18next
# or
yarn add @sonardigital/translations i18next react-i18next

What this gives you

  • Provider: TranslationsWrapper to wire translations and language into context
  • Hooks:
    • useTranslations to initialize i18n and expose { t, i18n, changeLanguage, language }
    • useTranslationsContext to read the shared context anywhere
    • useNamespaceT(namespace) to prefix keys like COMMONS.title
  • Utilities:
    • initializeI18n(resources, lng) and createI18nInstance(language, resources)
    • getDeviceLanguage()
  • Constants: DEFAULT_LANGUAGE, LANGUAGE_OPTIONS, LANGUAGE_STORAGE_KEY

Minimal example

import React from 'react';
import { createRoot } from 'react-dom/client';
import {
  TranslationsWrapper,
  useTranslationsContext,
  useNamespaceT,
  DEFAULT_LANGUAGE,
} from '@sonardigital/translations';

const resources = {
  en: { translation: { hello: 'Hello', COMMONS: { title: 'Home' } } },
  it: { translation: { hello: 'Ciao', COMMONS: { title: 'Home' } } },
};

function App() {
  const { t, changeLanguage, language } = useTranslationsContext();
  const tc = useNamespaceT('COMMONS');

  return (
    <div>
      <h1>{tc('title')}</h1>
      <p>{t('hello')}</p>
      <button onClick={() => changeLanguage(language === 'en' ? 'it' : 'en')}>
        Switch language
      </button>
    </div>
  );
}

createRoot(document.getElementById('root')!).render(
  <TranslationsWrapper language={DEFAULT_LANGUAGE} translations={resources}>
    <App />
  </TranslationsWrapper>
);

API

  • TranslationsWrapper props:

    • language?: string – initial language. If omitted, uses current i18next language
    • translations: Record<string, unknown> – i18next resources object { [lng]: { translation: { ... } } }
    • methods?: return of useTranslations to override provided methods
  • useTranslations({ language?, translations }){ t, i18n, changeLanguage, language }

    • Initializes i18n once with initializeI18n and keeps language in sync
  • useTranslationsContext() → same shape as above, from context

  • useNamespaceT(namespace: string)(key: string, options?) => string

    • Returns a t that prefixes keys with ${namespace}.
  • initializeI18n(resources, lng)

    • Sets up i18next with react-i18next; default ns is translation, useSuspense: false
  • createI18nInstance(language, resources)

    • Creates and returns a detached i18n instance (advanced/SSR)
  • getDeviceLanguage()

    • Returns browser language or DEFAULT_LANGUAGE
  • Constants: DEFAULT_LANGUAGE = 'it', LANGUAGE_OPTIONS, LANGUAGE_STORAGE_KEY

Resource shape

const resources = {
  en: {
    translation: {
      hello: 'Hello',
      COMMONS: { title: 'Home' },
    },
  },
  it: {
    translation: {
      hello: 'Ciao',
      COMMONS: { title: 'Home' },
    },
  },
};

Notes

  • The library disables escaping in interpolation (escapeValue: false) and disables React suspense in config.
  • If you already have i18next initialized, you can pass methods to TranslationsWrapper to reuse your instance and configuration.

License

ISC