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

@devoxa/i18next-test

v3.0.1

Published

Check `i18next` locale files for missing translations and common errors.

Downloads

310

Readme

Installation

yarn add @devoxa/i18next-test

Usage

i18next-test -c i18next-test.config.js
// i18next-test.config.js
module.exports = {
  // This is the default locale of your source files
  defaultLocale: 'en',

  // This is the path to your locale files on the file system, with the files named
  // following the `${localePath}/${locale}/${namespace}.json` pattern
  localePath: './public/locales',

  // This is the (unused) default namespace of your translations
  defaultNamespace: 'undefined',

  // (Optional) This is an array of regular expressions describing text that should not be in the
  // translations. It can be used for making sure that the overall voice of the translations
  // is consistent (e.g. that "sign in" is always used instead of "login").
  prohibitedText: [/\blog.?in\b/i],
}

Note that the configuration file has a similar structure to i18next-parser, so you can use a single file for both.

Contributors

Thanks goes to these wonderful people (emoji key):

This project follows the all-contributors specification. Contributions of any kind welcome!

License

MIT