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

init-env

v0.0.7

Published

initialize environment variables into process.env with a json file

Downloads

8

Readme

init-env

This module will initialize environment variables into process.env using a JSON file

Build Status

Requirements

By default, the module will look for a file in your root directory, .env.json, and use this to read a JSON object of values you want to use as environment variables.

eg.

file: .env.json

{
  "NODE_ENV": "development",
  "API_KEY": "dwdewd232ed23e2321ews12e1"
}

file: server.js

require('init-env')();
console.log(process.env.NODE_ENV) // --> development

Custom Configuration

You can pass custom configs to the module if the defaults don't match what you want to do.

Options

____________________________________________________
property:    logToConsole (Boolean)
default:     false          
description: this will let the module log messages
             about what its doing
____________________________________________________
property:    filePath (String)
default:     './.env.json'                
description: a file path relative to the root of
             the directory eg.  ./.env.json
____________________________________________________
property:    jsonPath (string)
default:     null              
description: property path to where the environment
             vars are located in the JSON
____________________________________________________
property:    overwrite (boolean)
default:     true              
description: when true this decide if the env var
             will be overwritten if already defined
____________________________________________________

eg.

filepath: ./.config/.env.json

{
  "config":{
    "envVars":{
      "NODE_ENV": "development",
      "API_KEY": "dwdewd232ed23e2321ews12e1"
    }
  }
}

file: server.js

require('init-env')({
  logToConsole:true,
  jsonPath:'config.envVars',
  filePath: './.config/.env.json',
  overwrite: true
});
console.log(process.env.NODE_ENV) // --> development

Notes:

  • report issues
  • pull requests are welcome