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

env-in-yaml

v1.0.1

Published

Simplest way to use environment variables in your .yml/.yaml files

Downloads

9

Readme

env-in-yaml

Simplest way to use environment variables in your .yml/.yaml files

Instalation

# with npm
npm install env-in-yaml

# or with Yarn
yarn add env-in-yaml

Usage and Example

First, you need to configure the .env file with the necessary variables, like the example below:

# .env
S3_BUCKET=myBucket
SECRET_KEY=ASBNAAYSTBAHAGSJA

Then configure and get the desired variable in your.yml/.yaml file. There are several ways and tools to do this, and I won't go into those details. Let's just assume that after setting up the .yaml file, you stored the url variable in the url constant

# .yaml
URL="www.google-${ENV:S3_BUCKET}.com${ENV:SECRET_KEY}"

Note that the variable to be substituted is between the delimiters "${ENV:" and "}" . You can override this setting by passing an options argument in the envInYaml function.

Once you get the variable you want in your .YML/.YAML file, just call the envInYaml function.

import { envInYaml } from 'env-in-yaml'

const url = 'www.google-${ENV:S3_BUCKET}.com${ENV:SECRET_KEY}'
const replaced = envInYaml(myVarFromYaml)
// output: www.google-myBucket.comASBNAAYSTBAHAGSJA

Release History

  • 1.0.0
    • Initial release

Contributing

Any help is extremely welcome and I would love it! Feel free to submit your PR!

Meta

Lucas Torres @olucasdev
Follow me on Github and Twitter and get in touch !!
I will love to talk about tech 😄!
https://github.com/torreslucas13