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

@webkrafters/react-hoc-memo

v1.0.0

Published

Memoizes all results to new HOC calls and returns them on subsequent calls.

Downloads

2

Readme

React-HOC-Memo

This package assists with the capture, caching and continued reuse of react Higher Order Components (HOC) type returned by a React HOC function.

Arguments to each new calls to the HOC function and the HOC type returned are cached and reused at subsequent calls to the HOC function bearing identical arguments.

npm i -S @webkrafters/react-hoc-memo

npm install --save @webkrafters/react-hoc-memo

Requirement

When the HocMemo::use method options.bypass argument is false (i.e. the default value), Component argument requires a valid displayName static property. The cache key is calculated using this property. To Components lacking this property such as those from 3p libraries, please add a unique displayName static propperty.

Usage

component.js

import React from 'react';

const Test = props => { ... };
Test.displayName = 'Test';

export default Test;

hoc.js

import React from 'react';
import HocMemo from '@webkrafters/react-hoc-memo';

const hocFunc = (Component, options) => {
    ...
    return props => {
	    ...
	    return (<Component  {  ...props  } />);
    };
};

const hocMemo = new HocMemo(hocFunc);
const hocFuncMemo = hocMemo.use.bind(hocMemo); // `hocMemo.use` arguments are passed through to the `hocFunc` function

export default hocFuncMemo;

app.js

import React, {Fragment} from 'react';
import hocFuncMemo from './hoc';
import Test from './component';

const WrappedTest = hocFuncMemo(Test); // `hocMemo.use` arguments are forwarded to the `hocFunc` function
const WrappedTest1 = hocFuncMemo(Test, { ... }); // `hocMemo.use` arguments are forwarded to the `hocFunc` function
const WrappedTest2 = hocFuncMemo(Test, { bypass: true /* to bypass the cache */, ... }); // `hocMemo.use` arguments are forwarded to the `hocFunc` function.
const WrappedTest3 = hocFuncMemo(Test); // WrappedTest3 === WrappedTest

const App = () => (
    <Fragment>
	    <WrappedTest  {  ...  } />
	    <WrappedTest1  {  ...  } />
	    <WrappedTest2  {  ...  } />
	    <WrappedTest3  {  ...  } />
    </Fragment>
);

export default App;

index.js

import React from 'react';
import ReactDOM from 'react-dom';
import App from './app';
ReactDOM.render(<App />, document.getElementById('root'));

Design Considerations

Decision to deliver this solution as a function closure versus a class instance was considered. Great factor in the decision was cpu time and memory usage. In large react applications, every bit of memory counts. Majority of professional applications, with every new additional feature, grows larger over time. Class instance delivery method was determined to provide a more efficient resource management.

License

ISC