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-internationalize

v1.1.0

Published

Internationalization for react

Downloads

4

Readme

react-internationalize

Internationalization for react

NPM JavaScript Style Guide

Demo

Install

npm install --save react-internationalize

Usage

import React, { Component } from 'react'

import {LanguageSelector, setLang, setSource, getSource, WithGetText, withI18n} from 'react-internationalize'

/**
 * First we define a source, it is a function which given the language code
 * and the string's key, returns the appropriate translated string
 *
 * this is an example implementation and you can do whatever you want
 *
 * sending a default value could be a great idea
 *
 * @param {code} lang The actual language code
 * @param {String} key The key of the string
 */
const simpleSource = (lang, key) => {
  return {
    hello: {
      'fr': 'Bonjour',
      'es': 'Hola',
      'en': 'Hello'
    },
    more: {
      'fr': 'Plus',
      'en': 'More',
      'es': 'Más'
    }
  }[key][lang]
}

/**
 * Another source for demonstrating source change
 */
const moreSource = (lang, key) => {
  return {
    hello: {
      'fr': 'Bonjour monsieur/madame',
      'es': 'Hola señor/señora',
      'en': 'Hello sir/madam'
    },
    more: {
      'fr': 'Moins',
      'en': 'Less',
      'es': 'Menos'
    }
  }[key][lang]
}

/**
 * Rendering this component nested in a WithGetText element, will provide
 * getText as a props
 */
class TextWithGetText extends Component {
  render () {
    return <b><p>{ this.props.getText('hello') }</p></b>
  }
}

/**
 * This Component will go through an HOC so that text is a translated prop
 */
class TextWithHOC extends Component {
  render () {
    return <b><p>{this.props.text}</p></b>
  }
}

/**
 * The wrapped component will have it's prop text being translated to the selected language
 */
const WithHoc = withI18n(TextWithHOC, {text: 'hello'})

class ChangeSourceBase extends Component {
  render() {
    return <b><p>{this.props.text}</p></b>
  }
}

const ChangeSource = withI18n(ChangeSourceBase, {text: 'more'})

/** Set the actual language to french (default is english) */
setLang('fr')
/** Set the source to our previously defined source function */
setSource(simpleSource)

export default class App extends Component {
  render () {
    return (
      <div>
          <div>
            {/**
                 * LanguageSelector handles everything on it's own, or can be controlled, or you can roll your own
                 * You could also detect user's preference in the browser or from a persisted source, etc...
                 */}
            <h2>Language selection widget (not mandatory)</h2>
            <LanguageSelector codes={['en', 'fr', 'es']} />

            {/**
                 * WithGetText inject a getText props which allow the component to retrieve the translated string
                 * This will also make the component re-render when language or source changes.
                 * It is the responsibility of the component to call getText
                 */}
            <h2>Using WithGetText</h2>
            <WithGetText>
              <TextWithGetText />
            </WithGetText>

            {/**
                 * When a component goes through the withI18n HOC, it get's injected with translated props
                 * This will also make the component re-render when language or source changes.
                 * he component can use it's props as if they were translated or not
                 */}
            <h2>Using withI18n hoc</h2>
            <WithHoc />

            {/**
                 * An example of how to change the language
                 */}
            <h2>Custom Language change</h2>
            <button onClick={(event) => {
              event.preventDefault()
              setLang('es')
            }}><p>We no speak americano</p></button>

            {/**
                 * An example of how to change the source
                 */}
            <h2>Changing Language string's source</h2>
            <button onClick={(event) => {
              event.preventDefault()
              if(getSource() === simpleSource){
                setSource(moreSource)
              } else {
                setSource(simpleSource)
              }
            }}> <ChangeSource /> </button>
          </div>

      </div>
    )
  }
}

License

MIT © MaxLarue