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

assert-dotenv

v3.0.0

Published

One fell swoop for loading and asserting environment settings in node.

Downloads

37

Readme

assert-dotenv

assert-dotenv = dotenv + dotenv-assert

One fell swoop for loading and asserting environment settings in node.

Version 3.0.0

  • This module now fully supports sync and async execution
    • Synchronous execution throws errors (when errors)
    • Asnychronous execution passes errors to the error-first callback

Why use assert-dotenv

  • Storing configuration in the environment is one of the tenets of a twelve-factor app.
  • Implicit default settings can lead to confusing troubleshooting scenarios and should be avoided entirely.
  • The assert.env file only lists what environment settings (keys) are required without providing values like private tokens, passwords, etc. and therefore can and should be checked into version control repositories.
    • .env files contain setting keys and values, therefore, they should not be checked into version control repositories.

How does it work

An exception is thrown if any of these cases are true:

  • An assert.env (or otherwise specified) file is not found
  • The keys listed in the assert.env file are not set on the process.env node object

Otherwise, your environment settings are applied and your application executes as expected.

Installation

$ npm install --save assert-dotenv

Usage

/**
*  Synchronously load .env and assert.env files from CWD or
*  from the nearest parent directory where they are found.
*/
require('assert-dotenv')();

/**
*  or, specify custom file locations and/or file names
*
*  CAVEAT: specifying a filename (without a path) will cause
*  the file to be loaded from CWD or the nearest parent
*  directory where it is found.
*/
require('assert-dotenv')({
  dotenvFile: '../configs/.env.staging',
  assertFile: 'assert.env.staging'
});

/**
*  Asynchronous execution occurs when you provide a callback
*/
require('assert-dotenv')(function(error){
  if(error) throw error;

  console.log('Environment Settings Loaded and Asserted!');
});

/**
*  also, you can async with options
*/
require('assert-dotenv')({
  dotenvFile: 'dev.env',
  assertFile: 'assert.dev.env'
}, function(error){
  if(error) throw error;

  console.log('Environment Settings Loaded and Asserted!');
});

Simple HTTP Server Example

  • ~/app/.env

    IP=127.0.0.1
    PORT=1337
  • ~/app/assert.env

    IP
    PORT
  • ~/app/index.js

    • Synchronous Example

      require('assert-dotenv')();
      
      var http = require('http');
      
      http.createServer(function(request, response) {
        response.writeHead(200, {'Content-Type': 'text/plain'});
        response.end('Hello World\n');
      }).listen(process.env.PORT, process.env.IP);
      
      console.log('==> Server running at http://' + process.env.IP + ':' + process.env.PORT + '/');
    • Asynchronous Example

      require('assert-dotenv')(function(error) {
        if(error) throw error;
      
        var http = require('http');
      
        http.createServer(function (request, response) {
          response.writeHead(200, {'Content-Type': 'text/plain'});
          response.end('Hello World\n');
        }).listen(process.env.PORT, process.env.IP);
      
        console.log('==> Server running at http://' + process.env.IP + ':' + process.env.PORT + '/');
      });
  • Start the server and see that all is well

    $ node ~/app/index.js
    ==> Server running at http://127.0.0.1:1337/

LICENSE

ISC License (ISC)

Copyright © 2014-2015, Buster Collings

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.