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

envmanager

v1.1.3

Published

Manage environmental variables before running your server

Downloads

5

Readme

envmanager

Build Status Code Climate

envManager is a npm module that allow you to specify, validate and check local environmental variables. It works best with dotenv as it was created for that.

Install

npm install envmanager --save

Usage

To use envmanager, you must create a file called .env_template on your root directory. This will allow envmanager to generate and test your env file. Your .env_template should just include each variable you would like to include in your .env such as:

database_uri
password
username

To add defaults for your .env, do the following

password=actualpassword

After your .env_template has been configured, you should run node ./node_modules/envmanager/envmanager.js generateEnv to generate your environment. For best practices for your developers, you should insert that command into your package.json as the following:

...
"scripts": {
  "env": "node ./node_modules/envmanager/generateEnv.js"
},
...

and run the program as npm run env.

In your program, as early as you can, usually just in your index.js, add the following code:

const envManager = require("envmanager");
const manager = new envManager();

if(manager.checkVariables()){
  // the rest of your code
}

Note, as of now the envmanager will throw an exception ending your program if variables are not properly assigned.

Testing

npm test

FAQ

Why did you make this program?

This system was originally built for HackMerced to allow student developers to easily get started on contributing to our projects.

Should I commit the .env file?

Please don't, add it to your .gitignore, otherwise people will get to it!