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-i18n-tools

v0.1.9

Published

## Getting Started

Downloads

16

Readme

React i18n Tools

Getting Started

Install the tool.

npm install --save react-i18n-tools

Then create a .i18nconfig file in the root of the project you would like to internationalize. Populate it with the content below, changing it as you see fit.

{
  "outputDirectory": "modules/translations/",
  "locales": [
    "es-ar"
  ],
  "rootComponentDirectory": "components/"
}

Initialize the Translated Text (<Trext />) component by passing it a component to wrap text with.

import { Text } from 'react-native'
import { Trext } from 'react-i18n-tools'

Trext({ Text: Text })

At the top level of your component tree (e.g., your App.js) add the <TrextProvider /> and pass it the current locale, as well as a mapping to your translations. For example,

const translations = {
  'es-ar': require('../modules/translations/es-ar.json')
}
const locale = 'es-ar'

// ...

render () {
  return (
    <TrextProvider translations={translations} locale={locale}>
      // ...
    </TrextProvider>  
  )
}

Trext Component

Wrap any text you would like to translate with the <Trext /> component. You can add styles to the text that will be stripped out when the text is exported for translation. You can also provide template variables—such as a name, demonstrated in the example below.

import { Trext } from 

// ... 

render () {
  return (
    <Trext name='world'>
      Hello, [color=red,italic,bold]#{name}[/b]!
    </Trext>  
  )
}

Exporting Text for Translation

From the CLI run

react-i18n

The text will be exported to the outputDirectory specified in your .i18nconfig file.