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

exhaustive-prop-types

v1.0.1

Published

Extend React PropTypes to check undocumented props at runtime.

Downloads

21

Readme

exhaustive-prop-types

Extend PropTypes to check undocumented props at runtime.

PropTypes checks at runtime the values of the described props. Some static checking tools (such as eslint-strict-react with the prop-types rule) can verify that component aren't using props not define in propTypes. However nothing checks if the component is given props not defined defined in propTypes.

exhaustive-prop-types checks at runtime that all received props are defined in your propTypes. It catches potentially extraneous or undocumented props. It helps refactoring and catching over-connected props from Redux.

Installation

npm install --save exhaustive-prop-types

Usage

Let's start with a simple component.

import React from 'react';

class MyComponent extends React.Component {
  render() {
    return (
      <div>
        My name is {this.props.name}.
      </div>
    )
  }
}

They are two equivalent ways of using exhaustive-prop-types. You can either extend your composant.

import PropTypes from 'prop-types';
import { exhaustive } from 'exhaustive-prop-types';

MyComponent.propTypes = {
  name: PropTypes.string.isRequired
};

const ExtendedComponent = exhaustive(MyComponent);

Or you can wrap your Component.propTypes with exhaustivePropTypes.

import PropTypes from 'prop-types';
import { exhaustivePropTypes } from 'exhaustive-prop-types';


MyComponent.propTypes = exhaustivePropTypes({
  numberProp: PropTypes.number
});

From there, if you provide a extra prop to your component.

<MyComponent name="Captain" age=42 />

You will get a warning:

Warning: Failed prop type: The prop `age` ins't defined in `MyComponent` propTypes.

Configuration

There is no configuration. It works with standard PropTypes checking, so it should warn only in development.