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

envdotyml

v1.2.3

Published

Load environment variables from a .env.yml file

Downloads

292

Readme

envdotyml

npm CI Status dependencies Status devDependencies Status

Load environment variables from a .env.yml file

Usage

Install envdotyml by running:

yarn add envdotyml

Then, at the top of a file that will be executed before you access any environment variables, add:

import 'envdotyml/set.js'

Alternatively, for more control over when environment variables are set:

import {parse, set} from 'envdotyml'

async function run() {
  // Reads environment variables and mutates `process.env`
  await set()

  // Returns the environment variables without mutating `process.env`
  const vars = await parse()
}

run()

The .env.yml is expected to be an associative array:

STRING: Hello World!
MULTILINE_STRING: |
  foo
  bar
  baz
ARRAY:
  - One
  - Two
  - Three
OBJECT:
  key: value

Strings are left as is. More complex values are converted to JSON strings.

If .env.yml does not exist, parse will return an empty object, and set will do nothing.