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

eslint-plugin-reactintl

v0.1.3

Published

Linting for react-intl components

Downloads

121

Readme

eslint-plugin-reactintl

An ESLint Plugin for the react-intl package. This was created initially to check that all instances of FormattedMessage as well as a definable array of custom components have a defaultMessage attribute. It satisfies this requirement with room for growth.

Installation

Inside your package, run npm install --save-dev eslint-plugin-reactintl to install and save the plugin as a dev dependency of your package.

Inside .eslintrc.js, add "reactintl" as a plugin. You can also extend the linter from just checking on the default FormattedMessage by adding to the components array.

module.exports = {
    "plugins": ["reactintl"],
    "rules": {
        "reactintl/default-message": ['error', {
            "components": [ "AnotherComponentToLint" ],
        }],
    },
}

Rules

  • default-message
    • ensures a component has defaultMessage and id supplied, unless the properties are added in a spread operator
    • define other components you want to apply the same linting on in the component property of the rule options ([ "AnotherComponentToLint" ])
    • documentation
  • contains-hardcoded-copy
    • ensures all nodes do not contain hardcoded copy / string literals.
    • not recommended to turn this all the time as it's very intensive, but it will save time in retrospectively adding FormattedMessage components to wrap around strings
    • documentation

Development

Directory Layout

  • src/lib/index contains the default rules and exports of the module
  • src/lib/rules contains individual rules consumed by the above config

Building

When running npm run build, we transpile all rules and the index from src/ to lib/ in the root.

Testing

Spec files are found inline with the source and md document. Run npm run test to run all tests in the package.

Publishing

Run npm publish to publish the latest version to NPM. Before this complete the prepublish script will run to test and build rules.


This code was based on the eslint-plugin-jsx-a11y code and follows code patterns I enjoyed there. It also consumes jsx-ast-utils, a utility modules for analysing JSX.