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

serverless-dynamic-dotenv

v1.0.2

Published

Dynamic environment management using Dotenv

Downloads

111

Readme

serverless-dynamic-dotenvnpm version

Dynamic environment management using Dotenv

You can use this plugin if you are storing your environment variables using dontenv module. This will allow you to reference env variables ${env:VAR_NAME} inside your serverless.yaml and it will load them into your lambdas.

Install and Setup

First, install the plugin:

> npm i -D serverless-dynamic-dotenv

Next, add the plugin to your serverless config file:

service: myService
plugins:
  - serverless-dynamic-dotenv
...

Now, just like you would using dotenv in any other JS application, create your file with stage name .env.stage_name in the root of your app:

DB=mongodb://username:password@host:27017
AWS_REGION=us-west-1
SOME_VAR=some_value

Plugin options

Dotenv config file names are dynamic. Files should be located in the root of the project (beside serverless.yaml) File names are based stage option: .env.stage If you run your serverless command with --stage dev option then plugin maps vars from .env.stage_name. So that, you can create one .env file per stage.

Usage

Once loaded, you can now access the vars using the standard method for accessing ENV vars in serverless:

...
provider:
  name: aws
  runtime: nodejs6.10
  stage: dev
  region: ${env:AWS_REGION}
...

Lambda Environment Variables

Again, remember that when you deploy your service, the plugin with inject these environment vars into any lambda functions you have and will therefore allow you to reference them as process.env.AUTH0_CLIENT_ID (Nodejs example).