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

envr

v2.1.4

Published

decide the environment the application is running in, loads config files

Downloads

10

Readme

envr

Checks for commandline parameters or environment variables to determine in which environment to run your application.

npm Travis node

Configuring the Environment

Reads the NODE_ENV variable

export NODE_ENV=production

values can be:

  • prodcution
  • live
  • integration
  • staging
  • testing
  • dev
  • development

where production === live, integration === staging and dev === development

The NODE_ENV variable is overriden by setting any of those flags:

--production (--live)
--integration (--staging)
--testing
--dev (--development)

API

Get the current environment

const envr = require('envr');

console.log(envr.env) // production, integration, testing or development

There are also methods to directl yquery the environment

const envr = require('envr');

envr.isProduction()
envr.isIntegration()
envr.isTesting()
envr.isDevelopment()

All of thoe methods throw errors if the environment was not set

Load environment aware js config files

Loads js config files from a directory using the pattern ${dirname}/config.${envr.env}.js. All toplevel properties of a config.js file that may reside in the same directory as the other config files will overrife properties of the environment specific config file. The configfiles msut export an obejct.

const envr = require('envr');

// async, __dirname is the dir containgin the configs
cosnt config = envr.config(__dirname);