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

should-not-update

v1.0.2

Published

Declarative shouldComponentUpdate wrapper

Downloads

15

Readme

ShouldNotUpdate

npm version Build Status Coverage Status

Simple component utilizing the shouldComponentUpdate lifecycle hook. Wrap it around child components that you don't want to rerender on property changes.

import ShouldNotUpdate from 'should-not-update'

const MyComponent = ({ someProp }) => (
  <ShouldNotUpdate>
    <InnerComponent someProp={someProp}>
      This is not updating on property change
    </InnerComponent>
  </ShouldNotUpdate>
)

Rendered component

By default, ShouldNotUpdate will render as a div element, but that can be changed by setting the component prop, which accepts either a tag name string (such as 'div' or 'span')

<ShouldNotUpdate component="ul">

or a React component type (a class or a function), which should render their children to be useful.

const MyComponent = ({ children }) => (
  <div>
    {children}
  </div>
)

<ShouldNotUpdate component={MyComponent}>

Exceptions to the rule

Sometimes you want child components to re-render under certain conditions. You can add these conditions by setting the exceptWhen prop.

const MyComponent = ({ someProp }) => (
  <ShouldNotUpdate exceptWhen={someProp === 42}>
    <InnerComponent someProp={someProp}>
      This only updates on property change when someProp is 42
    </InnerComponent>
  </ShouldNotUpdate>
)

Other properties

All properties besides children, component and exceptWhen are directly passed to the rendered component.

const MyComponent = ({ someProp }) => (
  <ShouldNotUpdate component="nav" role="navigation">
    <InnerComponent someProp={someProp}>
      This is not updating on property change
    </InnerComponent>
  </ShouldNotUpdate>
)

Use cases

Amongst others, one possible use case is not re-rendering static children of a react-motion spring animation on every animation frame.

import { Link } from 'react-router'
import { Motion, spring } from 'react-motion'

const OffCanvas = ({ isVisible }) => (
  <Motion style={{ left: spring(isVisible ? 0 : -250) }}>
    {style => <nav role="navigation" style={style}>
      <ShouldNotUpdate component="ul">
        <li><Link to="/">Home</Link></li>
      </ShouldNotUpdate>
    </nav>}
  </Motion>
);