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

funcache

v1.0.2

Published

cache function calls

Downloads

90

Readme

funcache

A helper tool to cache function results, based on lru-cache, inspired by memoizee.

Difference with memoizee

memoizee is very useful, but it lacks the ability for conditional caching and this is funcache mainly for.

One simple case of conditional caching is, saying there is an api that returns the result of a workflow, and you want to cache the api response only when the its status is completed. There is no direct way to achieve this by using memoizee as it doesn't deal with the function result. With funcache you can simply set the option like this:

cacheAgeGetter: (res) => {
  if (res.status === 'completed') return 0; // 0 means infinity
  return -1; // -1 means no cache
}

Install

npm install funcache

Usage

import funcache from 'funcache';

type Result = {
  error?: string;
  data?: string[];
}

const cachedFunc = funcache(async (arg: string) => {
  try {
    const data = await getData(arg);
    return { data };
  } catch (e) {
    return { error: e.message };
  }
}, {
  max: 100,
  async: true,
  primitive: true,
  cacheAgeGetter: (ret) => {
    if (ret.error) return -1;
    return 60000;
  }
});
const erroredResp = cachedFunc('nonexistId');
const erroredResp1 = cachedFunc('nonexistId'); // not cached
const resp = cachedFunc('id');
const resp1 = cachedFunc('id'); // cached

Options

  • max: The maximum size of the cache for this function. Default is Infinity. Setting it to 0 also makes it be Infinity.
  • primitive: If all the arguments are strings, use them to get the cache key directly instead of hashing. This should improve the performance a bit. Default is `false'.
  • async: To cache the resolved values instead of the returned promise. Default is false. You may probably always want it to be true for async functions.
  • cacheAgeGetter: An optional custom function to get the cache ttl (in milliseconds) based on the function return(resolved). Return -1 will cause no-caching at all. This will be passed to the set function of lru-cache. Default is 0. The example code above shows an use case for this option.