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

Cacher

v0.1.7

Published

Simple library for caching more complex function calls.

Downloads

5

Readme

Cacher

npm version GitHub version Build Status Dependencies devDependencies Code Climate Test Coverage

Simple library for caching more complex function calls.

Can be used with react not to trigger rerendering by constantly creating new functors for components props.
Yet it has no dependencies to React or any other lib.

Installation

npm install --save Cacher

Simple Example

Let's say You have a component that receives a functor and renders N subcomponents.
Each subcomponent receives a callback which is the functor called with the subcomponents index. You could write:

class Component extends React.Component {
  
    // ...
  
    render() {
        return Array(this.props.N).map(function(_, index) {
            return (
                <SubComponent
                    callback={function() { this.props.functor(index); }}
                />
            );
        });
    }
}

But this way every time You render Component each Subcomponent receives a new functor as callback and needs to rerender.

What if You could get the same functor every time You know You already had one like that?

Now you can! :)

import Cacher from 'Cacher';

class Component extends React.Component {
  
    // ...

    cacher = new Cacher()
        .functor(this.props.functor)
        .create();
  
    render() {
        return Array(this.props.N).map(function(_, index) {
            return (
                <SubComponent
                    callback={function() { this.cacher(index); }}
                />
            );
        });
    }
}

Voilà!
The first time this.cacher is called with an index it creates one callback function and returns it.
Every next time for the same index it just returns the one created before (same object/reference).

Object Oriented example

You can also add a context to the main functor.
Just use

.constext(object)

to make Cacher call object.functor(index) instead of functor(index).

Multiply callbacks example

Cacher is configurable to accept an additional function (called action) aside with index.
You just need to tell him which parameter will it be.
E.g.:

import Cacher from 'Cacher';

class Component extends React.Component {
  
    // ...

    cacher = new Cacher()
        .context(someObject)
        .functor(this.props.functor)
        .action(1)
        .create();
  
    render() {
        return arrayOfFunctions.map(function(someFunction, index) {
            return (
                <SubComponent
                    callback={function() { this.cacher(index, someFunction); }}
                />
            );
        });
    }
}

Now this.cacher(index, someFunction) will return something functionally identical to:

function() {
    someFunction();
    return this.props.functor.call(someObject, index);
}

Clearing cache

You can clear the inside cache:

function someFn(/* some arguments */) {
    /* do sth */
}
const cacher = new Cacher().functor(someFn);
const getter = cacher.create();

const f34 = getter('34');

/* use getter */

cacher.clear();
const f34_prim = getter('34');
// Here ( f34 !== f34_prim )

Additional/Call/Runtime arguments

Also additional arguments can be passed.

const base = {};
function addError(component, error) {
    if (!base[component]) { base[component] = [] }
    if (base[component].includes(error)) { return; }
    base[component].push(error);
}

const getter = new Cacher().functor(addError).create();

getter('component1')('sth');
getter('component1')('probably');
getter('component2')('could be');
getter('component1')('wrong');
getter('component1')('wrong');

expect(base).to.deep.equal({
    'component1': ['sth', 'probably', 'wrong'],
    'component2': ['could be']
});

More to it

You can index by any simple type:

  • number
  • string
  • reference

Remember !

The function returned by create assumes the first argument it gets is the index, by which Cacher distinguishes cached material.

Final words

Feel free to comment and add suggestions.

This is my first lib I created and published to see how NPM works.
I am eager to enhance it if it proves useful to someone.