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

aws-secret-to-env

v1.3.1

Published

Create repositories using Mongo to retrieve and store Entities.

Downloads

26

Readme

CD Build

aws-secret-to-env

This JavaScript library aims to fetch access credentials stored in AWS service called AWS Secrets Manager and generate a .env file that contains the necessary environment variables for the development of your application.

Using

    $ npx aws-secret-to-env

When the library is called using the command above, it reads by default the .env.example file in the current directory, which must contain the following lines:

# service name exactly as defined in AWS Secrets Manager
SVC_NAME=

# Tokens found under "Command line or programmatic access"
AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY_ID=
AWS_SESSION_TOKEN=

These lines are read to obtain the necessary information to access the AWS Secrets Manager.

If the developer wants the library to read another file, they can pass it as a parameter in the command call, for example:

    $ npx aws-secret-to-env --envFile .env.test

In this case, the library will read the .env.test file instead of the .env.example file.