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

envine

v1.0.6

Published

A package to handle external config files (.env or .genv)

Downloads

12

Readme

Envine:

Envine is a package for easily importing environment configuration files.

Usage:

const envine = require('envine');
envine('./.env'); // loading a regular .env config file
envine('./env.json'); // loading a custom JSON object in environment

Env files:

Env files contains KEY=VALUE entries, separed by a '='. The files may also contain comments, starting with '#'.

In example.env, the comment is simply ignored, and FOO2 is not added to process.env:

FOO=BAR
#Comment
#FOO2=BAR2

API Methods:

envine(fname = '.env'): process.env

> Reads a configuration file 'fname', and parses its content, 
  adding key-value properties to the current 'process.env'.
> It is possible to pass either JSON, ENV, GENV, and any other file 
  using ENV config notation.
> Returns a reference to 'process.env'.

Example usage:

// Declare and initialize the module
const envine = require('envine');

// Example 1:
// Loads a regular '.env' file, containing the property 'FOO=BAR':
// As '.env' is the default, there's no need of passing a filename,
//   but, it beheves the same as "envine('.env')"
envine(); 

// Acessing 'process.env.FOO' is now possible
console.log(process.env.FOO) //=> 'BAR'

// Example 2:
// Loads a custom 'env.json' file: "{ FOO2:'BAR2' }"
envine('env.json');

// Acessing 'process.env.FOO2' is now possible
console.log(process.env.FOO2) //=> 'BAR2'