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

try-cache

v1.0.12

Published

An auto-caching npm package for super-fast retrieval of less-consistant data

Downloads

64

Readme

try-cache

npm NPM Snyk Vulnerabilities for npm package npm

An auto-caching npm package for super-fast retrieval of data that doesn't have to be atomically consistant, allowing automatic cache update and expiration according to the user's needs.

Installation

npm i --save try-cache

Options

Initiation options

/**
 * @param silent - if true, don't log anything to the console. Defaults to false.
 * @param expire - the default expiration time in seconds. Defaults to 5 mins.
 */
export type TCOptions = {
  silent: boolean;
  expire: number;
};

Operation Options

/**
 * @param expire - the expiration time in seconds for the specific operation. Default to TCOptions' expire.
 * @param callbackFunction - the function to call if the retrieveFunction throws an error after cache failed. Defaults to "do nothing".
 * @param forceDB - if true, will force the retrieveFunction to be called even if the key is found in cache. Defaults to false.
 */
export type OperationOptions = {
  expire: number;
  callbackFunction: Function;
  forceDB: boolean;
};

Usage Example

import { TryCache } from 'try-cache';

// Sets the expiration to 20 seconds, and alerts on calls
const cb = new TryCache('redis://localhost:6379', { silent: false, expire: 20 });

// Initiates the connection to redis
await cb.initTryCache();

// Should take 3 seconds
const res1 = await cb.tryCache('myKey', () => dummyDB(2, 7));
console.log('First time result:', res1);

// Should take a few ms because cahe is saved
const res2 = await cb.tryCache('myKey', () => dummyDB(2, 7));
console.log('Second time result:', res2);


// dummyDB simulates a database call
async function dummyDB(x: number, y: number) {
  await sleep(3000);

  return { x, y };
}

To run the package locally with the example:

  1. Run the docker-compose (or run redis locally manually): docker-compose -f "src\miscellaneous\docker-compose.yml" up -d --build
  2. Run the example: npm run example

The output should show the different use-cases of the package (with and without cache at the beginning)

  • Notice! The third and fourth runs should successfully fail as they simulate the failure of the original db retrieval function.