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-update-checker

v0.1.1

Published

Console warnings for when a React component updates even though the props/state are deeply equal.

Downloads

4

Readme

react-update-checker Build Status

Console warnings for when a React component updates even though the props/state are deeply equal.

Example image

Install

$ npm install react-update-checker

Usage

For components that extend React.PureComponent, simply change the parent class to ReactUpdateChecker instead.

import ReactUpdateChecker from 'react-update-checker';

- class MyComponent extends React.PureComponent { }
+ class MyComponent extends ReactUpdateChecker { }

The above also works for components extending React.Component but do not implement a shouldComponentUpdate method.

If your component does have a shouldComponentUpdate method, extend the ReactUpdateChecker class and call the super method as the first statement in your shouldComponentUpdate

import ReactUpdateChecker from 'react-update-checker';

- class MyComponent extends React.Component {
+ class MyComponent extends ReactUpdateChecker {

    shouldComponentUpdate(newProps, newState) {
+     super.shouldComponentUpdate(newProps, newState);

      // existing shouldComponentUpdate logic here
    }
}

API

When process.env.NODE_ENV === 'production', the default export of this package will simply be React.PureComponent. This prevents blasting the console messages unexpectedly in a production environment.

ReactUpdateChecker

import { ReactUpdateChecker } from 'react-update-checker';

class MyComponent extends ReactUpdateChecker {}

The named export is identical to the default export, except it always returns the custom class, regardless of process.env.NODE_ENV.

getFailedKeys(object1, object2)

import { getFailedKeys } from 'react-update-checker';

const sameReference = {};

const oldProps = {
  id: 'some-id',
  letters: ['a', 'b', 'c'],
  obj: sameReference
};

const newProps = {
  letters: ['a', 'b', 'c'],
  obj: sameReference
};

getFailedKeys(oldProps, newProps);
// => ['letters']

Given 2 objects, returns a list of property keys where the corresponding values are deeply equal but not shallowly equal. These are typically the prop/state items that need to be adjusted to avoid a re-render. Note that this only checks properties that are common between both objects. Any new or removed properties are not included in the return value.

isShallowEqual(object1, object2)

import { isShallowEqual } from 'react-update-checker';

isShallowEqual({ foo: 'bar' }, { foo: 'bar' });
// => true

Given 2 objects, returns whether or not all top-level properties are equal. This is the exact same shallow comparison that is done by React.PureComponent, just re-exported in this module for convenience.

What about why-did-you-update?

You should probably just use that project instead. I originally needed something more targeted (no monkey-patching React) and needed it to be painfully obvious which prop/state names were causing the problem.

License

MIT