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

aws-cfg

v1.0.6

Published

Allows a user to store AWS-runtim specific configuration per lambda function in known dynamodb table

Readme

aws-lambda-config-node

Generic function for storing config for lambda functions. In point of fact it's not lambda specific, but this was the inspiration from my own end for writing it.

Why did you write this?

When using AWS Lambdas you have a problem of dealing with multiple accounts and configuration.

Where do I store my data? Either as a packaged config file in your lambda definition (YUCK) or You use something like this.

Grab a single config

So the code is quite simple and returns a promise containing the the config object retrieved from the dynamodb table in question.

var cf = require('aws-cfg');

cf.config({
  configName: '$LATEST:someConfig',
  tableName: 'sharedConfigTable',
  region: 'eu-west-1',
  debug: false
})
.then(function(d) {
  console.log('This is the d: %j', d);
});

This returns the "config" element from the 'sharedConfigTable' table where the configName field (the primary key) is equal to "$LATEST:someConfig"

Grab multiple configs

Sometimes you want to grab multiple configurations and leave them sorted by their respective configNames. Consider the following:

cf.setDefaults({
  tableName: 'sharedConfigTable',
  region: 'eu-west-1',
  debug: false
});

cf.mergeConfigs([
  '$LATEST:firstProject',
  '$LATEST:secondProject',
  {
    configName: '$LATEST:third-private',
    tableName: 'PrivateConfigTable',
    region: 'eu-west-1',
    debug: false
  }
])
.then(function(d) {
  console.log('This is the d: %j', d);
})

Here we've called mergeConfigs instead of the single config function. This will iterate over the list sent to it. Here i've sent both strings (the configName) and an object to merge configs. If you send a string then you must have called setDefaults prior. Otherwise you simply send an object that contains at least configName and tableName.

This will like above fetch them all, but will return as a single hash where each configNames points to its own "config" hash.

Table setup

Simply a two column dynamodb table:

  • column 1 is the primary key (no sort needed): configName
  • column 2 contains the config (type map) itself and is called: config