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

react-locales

v1.0.29

Published

Simple framework for translations

Downloads

34

Readme

Use Locale

Simple framework for translations. Statically typed.

Installation

  • The full thing
npm i react-locales @moveread/router-tools preferred-locale
yarn add react-locales @moveread/router-tools preferred-locale
  • Simplified, w/o language detection nor routes
npm i react-locales
yarn add react-locales

Usage

  1. Define what locales you want
// locales.ts
import { make } from 'react-locales'
import { provider } from 'react-locales/provider'
export const framework = make(['en', 'es', 'ca'], { fallback: 'en' })
export const { LocaleCtx, useLocale, locales, DefaultProvider } = framework
export const LocaleProvider = provider(framework)

// or use the `DefaultProvider` with the basic installation
  1. Wrap app in provider
// {main|index}.tsx
import { LocaleProvider } from './locales.ts'

ReactDOM.createRoot(document.getElementById('root')!).render(
  <LocaleProvider defaultLocale='en'>
    <App />
  </LocaleProvider>
)
  1. Define translations where they're used or elsewhere
// MyComponent.tsx
import { useLocale, t } from './locales.ts'

const subtitle = t({
  en: 'Hello',
  es: 'Hola',
  ca: 'Hola',
  ...
})

function MyComponent() {

  const { t, setLocale } = useLocale()

  const title = t({
    en: '...',
    ca: '...',
    es: '...',
    fr: '...',
    it: '...'
  })

  return (
    <div>
      <h1>{title}</h1>
      <h2>{t(subtitle)}</h2>
      <button onClick={() => setLocale('en')}>EN</button>
    </div>
  )
}

Advanced Usage

react-locales/provider is just one of the infinitely many possible provider combinations. To select the default locale, it uses the following, in order:

  1. The :locale route parameter
  2. localStorage.getItem('locale')
  3. The detected preferredLocale() (using preferred-locale)
  4. The defaultLocale prop

But you can stack these arbitrarily, even passing your own provider. For example, let's say you want to give localStorage priority over the route parameter:

import { make } from 'react-locales'
import { localStorageProvider } from 'react-locales/local'
import { routedProvider } from 'react-locales/routed'
export const framework = make(['en', 'es', 'ca'], { fallback: 'en' }) // eslint-disable-line
export const { LocaleCtx, useLocale, locales, DefaultProvider, makeT, t } = framework // eslint-disable-line

export function LocaleProvider() {
  return (
    <DefaultProvider defaultLocale='en'>
      <RoutedProvider>
        <LocalStorageProvider>
          {children}
        </LocalStorageProvider>
      </RoutedProvider>
    </DefaultProvider>
  )
}

As they're written, each provider uses the wrapping context as a fallback default So, you can define a custom provider as:

function MyLocaleProvider({ children }) {
  const { locale: defaultLocale } = useLocale()
  
  const [myLocale, setMyLocale] = useState(defaultLocale)

  return (
    <LocaleCtx.Provider value={{ locale: myLocale, setLocale: setMyLocale, t: makeT(myLocale) }}>
      {children}
    </LocaleCtx.Provider>
  )
}

And then nest it at whatever level you want according to the required priority, e.g:

<DefaultProvider defaultLocale='en'>
  <MyLocaleProvider>
    <RoutedProvider>
      <LocalStorageProvider>
        {children}
      </LocalStorageProvider>
    </RoutedProvider>
  </MyLocaleProvider>
</DefaultProvider>