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

@nicholaskuchiniski/serverless-dotenv-plugin

v2.0.1

Published

Serverless plugin template

Downloads

9

Readme

@nicholaskuchiniski/serverless-dotenv-plugin

Create .env files on your serverless function using serverless.yaml definition

npm version Run tests

Why ?

The main objective of this library is to get out of the lambda limit 4KBs problem, using the serverless.yaml definitions to assemble the .env file (allowing to get variables through SSM, etc.). Keep in mind that putting a .env in your lambda, also means putting all your environment variables in a readable way inside your lambda .zip, so be careful.

Usage

  • Install the plugin with yarn add -D @nicholaskuchiniski/serverless-dotenv-plugin

  • Add the plugin on you serverless.yaml:

    plugins:
      - "@nicholaskuchiniski/serverless-dotenv-plugin"
  • Create a custom definition on your serverless.yaml:

    custom: 
      dotenv: 
        API_URL: http://api-url.example.com
  • Run serverless dotenv, a .env file will be created on the root your actual directory and serverless will put it inside your lambda (is important to have dotenv propertly configured inside your code)

Example

Inside the main repository, a /example exists with a simple serverless function that shows a value from the .env file.