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-purerender

v0.1.0

Published

the purerender mixin in a decorator compatible way

Downloads

23

Readme

Build Status

It's just syntax sugar. It does a few sanity checks and then sticks a shouldComponentUpdate function on your class.

import PureRender from 'react-purerender';

@PureRender
class Foo extends React.Component {
    // stuff
}

Sanity checks:

  • checks you don't call it on a falsy value (undefined)
  • checks the thing you call it on doesn't have shouldComponentUpdate

The latter differes from the mixin implementation, because merging the results of should component update functions is weird and confusing. If you need that, shouldComponentUpdate is exposed

class Foo extends React.Component {
  shouldComponentUpdate(){
    return PureRender.shouldComponentUpdate.call(this, ...arguments) || magicGlobalThingWasChanged();
  }
}

Or react-mixin:

import {shouldComponentUpdate} from 'react-purerender';
import reactMixin from 'reactMixin';

@reactMixin.decorate({shouldComponentUpdate})
class Foo extends React.Component {
    shouldComponentUpdate(){
      // what happens if I return false and PureRender returns true?
      // I dunno... try it I guess, hope there's a test
    }
}

That's it really, file an issue if you notice an edge case. I wrote this because I need it for most of my components and I've switched to es6 classes.