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-lambda-s3-dotenv

v0.1.1

Published

npm module for easily loading dotenv files from cache, or S3 as origin

Readme

aws-lambda-s3-dotenv

Build Status Coverage Status

AWS's Lambda functions are incredibly powerful constructs for any cloud architecture. Coupled with versions and aliases, Lambda is well-suited for many use cases.

However...

Since environment variables are tied to a function's version, and not its alias, it makes it really difficult to do things like use the same Lambda function but point it at different environments (e.g. Dev, QA, Prod). Barring this functionality, this module will read configuration from an S3 bucket, store it in a path you specify (inside of /tmp), and either read the config from the filesystem cache, or refresh from S3.

A common way of loading configurable environment variables is the popular module dotenv. As such, this module will first check to see if there's a .env file in a cache location you specify (again, this should be prefixed with /tmp if you are running this on Lambda, as this is the only writable filepath). If it cannot find a local file to use, it will fetch a file from S3 and save it to the cache location.

TIP: It is helpful to pass the cache location as an environment variable separate from dotenv, as you can use something like CONFIG_LOCATION = .env for development on your local machine and CONFIG_LOCATION = /tmp in Lambda.

NOTE:: The localPath passed into the module should be relative to the root of your project. For example, if you are trying to load a file located at project/subdir/.env and your source file is located at project/subdir/index.js, your localPath should be ./subdir/.env, as opposed to ./.env or similar.

Installation

npm install aws-lambda-s3-dotenv

Usage

const loadConfig = require("aws-lambda-s3-dotenv");

exports.handler = function (event, context, callback) {
    let cacheLocation = ".env";
    loadConfig(cacheLocation, "s3-bucket", "s3-bucket-key", function(err) {
        if (err) console.log(err);
        else {
            require('dotenv').config({path: cacheLocation});

            // Do stuff with your environment variables
            
            callback();
        }
    });
}

Tests

npm test