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 🙏

© 2024 – Pkg Stats / Ryan Hefner

decode-env

v1.0.0

Published

Decode environment variables by name

Downloads

5

Readme

decode-env

A micro-library for decoding environment variables by name.

What?

This library provides a function which will decode specific environment variables, according to name patterns, into usable plaintext environment variables. By default, it will base64-decode all environment variables named like <FOO>_BASE64 into plaintext variables named like <FOO>. If the variables already exist, they will not be overwritten.

Why?

AWS Lambda environment variables may not contain commas. Certain types of secret strings commonly passed via environment variables, such as MongoDB connect strings, may contain commas. AWS CloudFormation templates provide an intrinsic function Fn::Base64 for base64-encoding values. To work around the limitation of Lambda, we may for example encode a MongoDB connect string into environment variable MONGO_URI_BASE64 in our CloudFormation template and run the decodeEnv function once at the beginning of our Lambda handler script to decode the value into another variable named MONGO_URI, as opposed to manually decoding it in every place that we use the value.

How?

For the base64 use case, simply require the module and run the decodeEnv function:

const decodeEnv = require('decode-env');

decodeEnv();

Or even more simply:

require('decode-env')();

For more complex use cases, you may specify an array of decoder mappings and an options object:

const decodeEnv = require('decode-env');
const mapping = require('decode-env/decoders/rot13').mapping;

decodeEnv([mapping], { overwrite: true });

The library includes decoder mappings for base64, rot-13, and uri-encoding, using the append strings BASE64, ROT13, and URLSAFE, respectively. You can easily write and employ custom decoder mappings as well.

Currently the only option supported is overwrite, which is a boolean indicating whether or not to overwrite existing environment variables. By default it is false.

For more usage details, see the examples.

License

This library is provided under the MIT License.