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

@avify/aws-env

v1.0.8

Published

This package allow the donwload of a .env file using AWS S3 Bucket

Downloads

17

Readme

@avify/aws-env

Npm repository for @avify/aws-env package that allow the donwload of an .env file using a S3 Bucket

Installation

npm install @avify/aws-env

Usage

You need the following environment variables to be set:

  • AWS_ACCESS_KEY_ID the access key id
  • AWS_SECRET_ACCESS_KEY the secret access key
  • ENV_BUCKET the name of the bucket
  • ENV_LOCATION the path for the .env file in the bucket

pakage.json example

{
   "scripts": {
      "configure": "aws-env",
      "build": "your build command"
   }
}

Also you can use another .env file to set the environment variables

AWS_ACCESS_KEY_ID=your_access_key_id
AWS_SECRET_ACCESS_KEY=your_secret_access_key
ENV_BUCKET=your_bucket
ENV_LOCATION=your_path/.env