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-memoized-context

v1.0.1

Published

Avoid unnecessary re-renders when consuming partially a React Context

Downloads

13

Readme

react-memoized context

npm version minzip Build Status MIT license

Avoid unnecessary re-renders when consuming partially a React Context.

  • < 1kb GZIP 🔬
  • Tree-shakable 🌴

Motivation

When a component has simple props, using PureComponent/Memo() is a possible solution to avoid extra re-renders from props coming from Context. However, components with complex props might perform worse when using PureComponent. It's in that moment that react-memoized-context rocks. It works like PureComponent/Memo() but it only performs the shallow comparison to props coming from Context.

See a Working Demo showing the benefits of react-memoized-context.

Installing

npm install react-memoized-context --save

Using

A. HOC

import { withMemoizedContext } from 'react-memoized-context';

const FootNote = ({ context, ...otherProps }) => {  
  /*... do stuff with context.name ...*/
}

// Only re-renders FootNote when UserContext.name changes.
const FootNoteContexted = withMemoizedContext(UserContext)(FootNote, ['name']);

B. Component renderProp

import { MemoizedContext } from 'react-memoized-context';

// Only re-renders FootNote when UserContext.name changes.
<MemoizedContext context={ UserContext } memoKeys={ ['name'] }>
    ({ name }) => <FootNote author={ name } />
</MemoizedContext>

C. Hook?

Well... the way React hooks work, it's impossible to directly subscribe to a part of the context value without re-rendering. See React issue #14110

function FootNote() {
  const { name } = useContext(UserContext);

  // FootNote re-renders when UserContext value changes, even if name is the same.
  <FootNote author={ name } />
}

Workaround

Use an extra hook useMemo as a wall between the Context part and the rest of the Component children. See React issue #15156.

function FootNote() {
  const { name } = useContext(UserContext);

  // Only re-renders FootNote when name is updated.
  return useMemo(() => (
    <FootNote author={ name } />
  ), [name])
}

See full Documentation with Demo.


Contributing

  • Development: yarn docz:dev
  • Testing: yarn test

Feel free to open an issue or PR.