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

environment-vars

v1.0.3

Published

Helper library to load environment variables from either process.env or a .env file

Downloads

585

Readme

Environment Variables made easy

This module is helpful if you have environment variables that get loaded in different way, depending on where the code is run. For example, if your tests run in a place where the environment isn't bootstrapped with all the required variables, but your production code runs in a place that is, this will help you out.

After you configure the module, and call .get('ENV_VAR_NAME'), the module first looks in process.env (the environment) to see if the variable is there. If it's not found there - and assuming you've set this module up to know where a .env file is - it will try to load the variable from .env

####Example Usage

// path is node's handy internal module for normalizing filepaths
var path = require('path');

var filePath = path.join(__dirname, '../../my_project_root');
var fileName = '.env';

var envVars = new EnvironmentVars(filePath, fileName);
var apiKey = envVars.get('SUPER_AWESOME_API_KEY');

Above, the envVars variable is configured to search for a file full of environment variables, located at __dirname, '../../my_project_root/.env'. An example .env file would look like this:

TEST_API_URL=http://localhost:4989
SUPER_AWESOME_API_KEY=xxxx-yyyy-zzzz

Passing in .env isn't required. The default is .env, so you really only need to pass in a 2nd option to the constructor if you use a file of a different name.

####Performance Considerations The module will cache the environment variable file after it's read from disk the first time. If you'd like to force it to re-read from disk, call the _resetCache method.

####Contributing PR's welcome :)