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 🙏

© 2026 – Pkg Stats / Ryan Hefner

simpledynamodbcache

v1.0.4

Published

Simple cache using DynamoDB

Readme

Simple DynamoDB Cache

I wrote this because I am using DynamoDB to store the backend data for a website but I also sometimes need to fetch information from slow legacy systems.

In the case that the cached data is "expired" whatever time period you determine that to be for you (in seconds) then you can fetch that legacy data and update the cache.

It will add a key to your object in dynamo, currently statically named 'last_fetch'

Usage:


//
// 60 		- The default cache timeout to use ( in seconds )
// 'us-east-1'  - How you would pass the region
//
var c = require('simpledynamodbcache')(60, 'us-east-1');

var parms = {
	TableName: 'mytable', 
	Key : { mykey_id : '12345' }
}

res = await db.get(parms).promise();		// Perform some query... 

//
// res looks something like:
//	Item: {
//		someObject: {
//			foo : 'bar'
//		}
//	}
//

if (c.cacheExpired(res.Item.someObject)) {

	// fetch from legacy ... 
	var freshValues = fetchFromLegacy();

	res.Item.someObject.foo = freshValues.foo;	// Update from legacy

	// Update in DynamoDB
	await c.cache('mytable', { mykey_id : '12345' } , 'someObject', res.Item.someObject);
}

// else it's not expired, just use it... 
return res;

Alternately for flat objects you can use cacheItem() which will put the updated Item with the timestamp added.


if (c.cacheExpired(res.Item)) {

        // fetch from legacy ...
	var freshValues = fetchFromLegacy();

	res.Item.foo = freshValues.foo;		// Update from legacy

	await c.cacheItem('mytable', res.Item);
}