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

use-lambda-env

v1.2.0

Published

Run a process with environment variables from an AWS Lambda function

Downloads

45

Readme

use-lambda-env

A quick CLI utility to grab environment variables from AWS Lambda functions, and execute shell commands with those environment variables.

Primary expected use-case: running a local development environment with config from a deployed lambda function, while avoiding the need to share secret files among developers. Developers would be expected to simply have AWS CLI access configured (preferrably with short-lived credentials), with Lambda:GetFunction permission to read the lambda function, along with KMS:Decrypt access to the environment variable encryption key used for the function (if applicable).

Example usage

use-lambda-env --region ap-southeast-2 your-function-name node index.js

I'd recommend putting the above in a script in package.json, so that developers don't need to remember it, and so you can update the function name for all developers easily when needed.

You can also just show the environment variables as a JSON blob by doing

use-lambda-env show --region ap-southeast-2 your-function-name

Contributing

This repository uses semantic-release. Please use the semantic commit message format for any contributions.

Code style / formatting is handled by ts-standard - please run npm run lint:fix to auto-fix your code before committing, or install StandardJS - JavaScript Standard Style VS code plugin to auto-fix every time you save.