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-intl-messages-linter

v0.0.1

Published

Lint react-intl messages used in your React components.

Downloads

6

Readme

react-intl-messages-linter

Install

yarn add --dev react-intl-messages-linter

Usage

lint-react-intl-messages [options] path

Command line options/flags

-q, --quiet [true]          Report errors only   
-i, --ignore                Pattern of files to ignore
--webpack                   Path to webpack config

Disclaimer

Note that this tool was made to help you spotting missing messages. It does not aim to replace proper unit/integrations tests you should have in most (if not all) cases. There are a couple of caveats and it may be unable to detect missing messages under unsupported circumstances or report a false positive.

Assumptions and caveats

  • Names of import specifiers must match the following regexp /[az]*messages$/i
  • Path of message imports must match /.*/[a-z-]*messages(?:.js)?$/i
  • Reasonable shadowing
  • Computed messages are not supported well... just yet
  • Messages with circular (imported) dependencies are not supported

TODO:

  • add some documentation :D
  • get rid of as many of above caveats as possible
  • make unsafe usages more robust and reliable
  • add feature to ignore files

LICENSE

MIT