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

envbang-node

v0.0.1

Published

Ensure that you have the correct environment variables available.

Downloads

13

Readme

EnvBang for Node.js

Build Status Code Climate

Ensure you have all the right environment variables set in your app.

Installation & Usage

As early as possible in your application require envbang and pass it your required environment variables.

EnvBang = require('envbang-node');
envbang = new EnvBang(['NODE_ENV', 'PORT', 'MONGOHQ_URL']);
// Once initialized, run #check() to ensure your environment variables are present
envbang.check();

If you are missing any environment variables, envbang will throw an error and give you a list of the variables you're missing:

The following required environment variables are missing:
=> NODE_ENV
=> PORT
=> MONGOHQ_URL

Inspiration

This package is meant to be used as a companion to dotenv-node. We are big fans of configuration via environment variables, but it can occasionally get a little crazy when you have a team of developers trying to keep up with changes to a .env file. The goal is to give clear feedback on application configuration to help reduce developer confusion and frustration.

References

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

Running tests

npm install
npm test