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

@kporten/intl-message-check

v1.1.1

Published

CLI tool to check if messages are unused or missing

Downloads

5

Readme

intl-message-check

This CLI tool can help you detect missing or unused react-intl messages (https://formatjs.io/docs/react-intl/api#formatmessage).

Run npx @kporten/intl-message-check in your JavaScript or TypeScript project to check your message definitions.

Requirements

  • Node.js LTS 14.x

Modes

  • Find missing -> Messages used in the code but not defined in the definition.
  • Find unused -> Messages not used in the code, but defined in the definition.

Example to find missing messages

Your JSON file with intl message definitions

{
  "language": "Language",
  "menu": "Menu",
  "notfound.back": "Back"
}

Your JS(X) or TS(X) code with formatMessage()

<div>{intl.formatMessage({ id: 'message' })}</div>

or

<div>
  {condition
    ? intl.formatMessage({ id: 'message1' })
    : intl.formatMessage({ id: 'message2' })}
</div>

or

<div>
  {intl.formatMessage(
    condition
      ? { id: 'message1' }
      : { id: 'message2' },
  )}
</div>

Run the tool

npx @kporten/intl-message-check
[1/3] What kind of messages do you want to find?

Find missing

[2/3] Please enter the path to your JS/TS project directory:

/path/to/your/project
✓ Path is valid

[3/3] Please enter the path to your JSON file with message definitions:

/path/to/your/project/src/i18n/en.json

languages.de
languages.en

Now you know that you should add the two missing messages to your definition file.

Note: Currently only static message IDs will be supported (id property and message string must be in the same line).


MIT License

Copyright (c) 2020 Kevin Porten