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

runtime-env-resolver

v1.2.1

Published

Resolve environment variables dynamically at runtime from remote stores (e,g, AWS SSM) or custom providers.

Readme

runtime-env-resolver

Overview

runtime-env-resolver lets you store environment variables as placeholders (e.g. ssm:/my/db/password) and resolve them at runtime from different sources such as AWS SSM Parameter Store, HashiCorp Vault, or your own custom provider.

✅ Keep secrets out of .env files
✅ Works with cloud & local environments
✅ Built-in support for AWS SSM (ssm: prefix)
✅ Extend with your own providers


Install

npm install runtime-env-resolver

Usage

1. Built-in Provider (AWS SSM)

(Requires @aws-sdk/client-ssm)

import { resolveEnvVariables, SSMProvider } from 'runtime-env-resolver';

// Works on AWS (Lambda, EC2) if IAM role has SSM permissions.
// For outside AWS: new SSMProvider({ region, credentials })
await resolveEnvVariables(new SSMProvider());

Before (process.env):

DB_PASSWORD=ssm:/myapp/db/password

After (process.env):

DB_PASSWORD=super-secure-password-from-ssm

2. Custom Provider

import { resolveEnvVariables } from 'runtime-env-resolver';

await resolveEnvVariables({
	shouldResolve(value) {
		return value.startsWith('custom:');
	},
	async resolve(values) {
		// Strip prefix
		const noPrefix = values.map((v) => v.replace('custom:', ''));

		// apply your own logic
		// NOTE: ensure to preserve order of values in the same order as the original array
		return noPrefix;
	},
});

Before (process.env):

DB_PASSWORD=custom:db-password-123

After (process.env):

DB_PASSWORD=db-password-123

Contributing

PRs and issues are welcome! Fork the repo and open a pull request.

License

MIT License – see LICENSE.

Resources

  • NPM: https://www.npmjs.com/package/runtime-env-resolver
  • GitHub: https://github.com/Maged-Zaki/runtime-env-resolver