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-i18next-components

v1.4.0

Published

A collection of React components and utilities to simplify react-i18next

Downloads

296

Readme

react-i18next-components

A collection of React components and utilities to simplify react-i18next.

Getting Started:

configureI18n

First you'll need to configure the initialization of the i18n React provider. We provide some defaults on top of the i18next configuration but you can override any property as necessary. Options and their defaults can be found here.

Reference on how locale files should be structured can be found here.

The call to configureI18n must be made before the use of any formatting component.

import { configureI18n } from 'react-i18next-components';
import App from './App'; // your entry page
import ​en from './locales/en';

const App extends React.Component {
  componentWillMount() {
    configureI18n({
      lng: 'en',
      resources: {
        en: {
          translation: en
        },
      }
    })
  }

  render() {
    // ...
  }
}
);

How to use:

All formatting elements can either be used by themeselves which will render a React fragment with the formatted content or with the render prop pattern to inject formatting into elements like text inputs.

Use as standalone component:

import { FormattedMessage } from 'react-i18next-components';

<FormattedMesage id="path.to.key" />;

Use with render prop:

import { FormattedMessage } from 'react-i18next-components';

<FormattedMesage id="path.to.key">
  {text => (
    <input type="text" placeholder={text} />
  )}
</FormattedMessage>

Components:

FormattedMessage

Given an id prop which indicates the path to the translation in your language file, the component will render the correct translation.

| Prop Name | Type | | --------- | ------ | | id | String | | options | Object |

import { FormattedMessage } from 'react-i18next-components';

<FormattedMesage id="path.to.hello" />;

// "Hello"

<FormattedMesage id="path.to.hello" options={{ name: 'Alec' }} />;

// "Hello Alec"

FormattedDictionary

Given any number of props each of which contain a path to a translation in your language file, the component will pass data in the same shape as the props to a child function. This component only supports the render prop pattern.

| Prop Name | Type | | --------- | ------ | | ... | String | | options | Object |

import { FormattedDictionary } from 'react-i18next-components';

<FormattedDictionary greeting="path.to.hello" closing="path.to.goodbye">
  {({greeting, closing}) => <p>{greeting}, {closing}</p>}
</FormattedDictionary>

// Hello, Goodbye

<FormattedDictionary greeting="path.to.hello" closing="path.to.goodbye" options={{ greeting: {name: 'Alec' }}}>
  {({greeting, closing}) => <p>{greeting}, {closing}</p>}
</FormattedDictionary>

// Hello Alec, Goodbye

FormattedDate

Given a value prop in any timestamp format, the component will render a formatted date or time in any format supported by moment.js. By default this component will render a date.

| Prop Name | Type | | --------- | ----------------------------------------------------------------------------------------------------- | | value | Any string supported by moment.js. | | format | Any localized format string supported by moment.js. |

import { FormattedDate } from 'react-i18next-components';

<FormattedDate value={Date.now()} />;

// "December 1, 2018"

<FormattedDate value={Date.now()} format="l" />;

// "12/01/2018"

<FormattedDate value={Date.now()} format="LLL" />;

// "December 1, 2018 1:08 PM"

FormattedTime

Given a value prop in any timestamp format, the component will render a formatted date or time in any format supported by moment.js. This component is similar to FormattedDate but it's default will be to render a time instead of a date.

| Prop Name | Type | | --------- | ----------------------------------------------------------------------------------------------------- | | value | Any string supported by moment.js. | | format | Any localized format string supported by moment.js. |

import { FormattedTime } from 'react-i18next-components';

<FormattedTime value={Date.now()} />;

// "5:00 PM"

<FormattedTime value={Date.now()} format="LTS" />;

// "5:00:00 PM"

FormattedRelativeTime

Given a value prop in any timestamp format, the component will render a human readable string displaying the relative time to the current time regardless of whether it's in the past or future. This string will automatically be translated based on the locale passed to lng on initialization.

| Prop Name | Type | | --------- | -------------------------------------------------------------------------- | | value | Any string supported by moment.js. |

import { FormattedRelativeTime } from 'react-i18next-components';

<FormattedRelativeTime value={1544227200} />;

// "in 7 days"

Contributing

Install locally:

This will install all dependencies and linting hooks.

npm install

Run tests:

We use a Jest test runner with enzyme.

npm test

Run locally:

Running this will spin up a local webpack server that watches for changes and will automatically rebuild the project for you.

npm start

Run locally against another project:

  1. Navigate into your application and make sure all existing depdencies are installed.
cd my-app
npm install
  1. Link the local version of the library to your application so that npm points to your local version rather than the app's node_modules folder.
npm link ../path/to/react-i18next-components
  1. Add the library to your apps dependency list in it's package.json, the version number should reflect the version in your local version of the library. Note, attempting to run npm install at this point may fail if the added version hasn't been published to the npm repository.
// ...
dependencies: {
  "react-i18next-components": "@latest",
}
// ...
  1. Import the components you want to test in your app.
import { FormattedMessage } from 'react-i18next-components';

// ...
const MyComponent = () => {
  return <FormattedMessage />;
};
  1. When you're finished developing you can unlink the project to re-point to the remote version of the package.
cd my-app
npm unlink ../path/to/react-i18next-components