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

@naturacosmeticos/eslint-plugin-i18n-checker

v1.0.1

Published

Helps you identify what locales keys are not included in your locales files

Downloads

2,160

Readme

eslint-plugin-i18n-checker

Known Vulnerabilities Build Status Codacy Badge

This eslint plugin helps you identify what locales keys are not included in your locales files.

Considering the follow scenario:

--locales/
----en-us.json
----es-pe.json
----pt-br.json
--src/
-----components/
-------header.js

In your header.js you have a call to your i18n function to get the localized value of the string logout: translate('logout')

The i18n-checker will verify if the logout is defined in each locale file you have.

How to use

Installation

npm i --save-dev '@naturacosmeticos/eslint-plugin-i18n-checker'

yarn add -D '@naturacosmeticos/eslint-plugin-i18n-checker'

Configuration

In your eslintrc file you need to add @naturacosmeticos/i18n-checker in the plugins section.

Options

You can configure the following options:

  • localesPath - string - your locales relative path (default is /locales/)
  • messagesBasePath - string - if your locales files has a base path you can pass it (default is undefined)
  • translationFunctionName - string - the name of your translation function (default is translate)

Example:

"@naturacosmeticos/i18n-checker/path-in-locales": ['error',
  {
    localesPath: 'public/locales/',
    messagesBasePath: 'translations',
    translationFunctionName: 't'
  }
]

Contributing

You can contribute submitting pull requests.

Setup

Install the dependencies running yarn in the project folder.

Lint

Just run yarn lint

Tests

You can run the following commands:

  • yarn test
  • yarn test:watch