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 🙏

© 2026 – Pkg Stats / Ryan Hefner

lets-i18n

v0.2.5

Published

easy i18n for next.js apps

Readme

How to use

  1. npm install lets-i18n

  2. Wrap your component tree with the TranslationProvider and pass to its translations prop the JSON file of translations.

  3. In the child component you want to translate, use the HOC withTranslations, then a t prop will be available so you can access your translation file.

  4. (Optional) A language prop is also available from withTranslations as well. In order to use it, pass the desired language to the TranslationProvider.

Example

index.js

export default class extends Component {
  render () {
    return (
      <TranslationProvider translations={this.state.translations} language={'pt-br'}>
        <MyApp />
      </TranslationProvider>
    )
  }

  componentDidMount () {
    const translations = require('./translations/pt-br.json')

    this.setState({ translations })
  }

  state = {
    translations: {}
  }
}

MyApp.js

const MyApp = (props) => <p>{props.t('hello.world')} - language: {props.language}</p>

export default withTranslations(MyApp)

translations/pt-br.json

{
  "hello": {
    "world": "Olá, Mundo"
  }
}

Development

For debugging purposes, when the NODE_ENV is not production, a translations prop is also available in the components wrapped by withTranslations with all the available keys and values:

const MyApp = (props) => {
  console.log(props.translations)

  return <p>{props.t('hello.world')} - language: {props.language}</p>
}

export default withTranslations(MyApp)

Errors

  1. Translation file not found: in a non-production environemnt it will not raise any error. In production it will print an error to the console:
console.error('TRANSLATION_ERROR: Please, provide the files to translate.')
  1. Translation key not found: it will raise different errors in production and other environments:

Production

The last property of the translation string will be rendered:

  <div>{t('this.translation.string.does.not.exist')}</div>

Will be rendered as:

  <div>exist</div>

Other environments

  <div>{t('this.translation.string.does.not.exist')}</div>

Will be rendered as:

  <div>TRANSLATION_ERROR: "this.translation.string.does.not.exist" does not exist.</div>

See more examples for React and next.js at the examples directory