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

@slsplus/dotenv

v0.1.2

Published

Serverless Dotenv Component

Downloads

30

Readme

Serverless Dotenv Component

npm NPM downloads

Introduction

Inspired by serverless-dotenv-plugin.

Preload environment variables into serverless. If you have variables stored in a .env file that you want loaded into your serverless yaml config. This will allow you to reference them as ${Dotenv.env.VAR_NAME} inside your config(If you ).

Setup

Add @slsplus/dotenv in your serverless.yml, as below:

Dotenv:
  component: '@slsplus/dotenv'

Now create .env file in the project root:

TENCENT_SECRET_ID=xxx
TENCENT_SECRET_KEY=xxx

ABC=124

Automatic Env file name resolution

By default, the component looks for the file: .env. If you want different env files based on environment. For example:

.env.development
.env.production

Then you can exec deploy command like:

$ NODE_ENV=development serverless --debug

Or, like this:

$ serverless --debug --env development

Inject custom arguments to command

You can directly run deploy command with custom arguments:

$ serverless --debug --custom abc --custom1 123

Then you can use by process.env.custom and process.env.custom1

Options

Complete configuration in serverless.yml

# serverless.yml

Dotenv:
  component: '@serverless/dotenv-component'
  inputs:
    envFile: /path/to/my/.env
    envPath: /path/to/my/
    exclude:
      - SECRET

Configuration description

| Param | Required/Optional | Type | Default | Description | | ------- | ----------------- | ------ | --------------- | ----------------------------------------------- | | envFile | Optional | String | .env | Dotenv file | | envPath | Optional | String | process.cwd() | Dotenv file path | | exclude | Optional | string | [] | Variable in .env file, you don't want to expose |

More Components

awesome-serverless-framework

License

Copyright (c) 2020 Serverless Plus