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

require-env-var

v0.1.3

Published

Easily require environment variables or else

Downloads

8,957

Readme

require-env-var

Easily require environment variables or else

Our projects are litered with environment variables. If we're doing things correctly, we're using a .env file and not checking it into source control. We're probably also using something along the lines of .env.example to track what variables should be set in our .env.

This may be fine when working solo or on a small team, but with larger projects it's easy to miss changes to .env.example. Furthermore, undefined environment variables don't always present themselves in the most obvious of ways.

require-env-var is a small library that helps with that. It allows you to specify which environment variables are required, and if they don't exist you get an error message telling you what key is missing. Additionally, it provides support for specifying multiple keys (first one wins) as well as a fallback in case no keys are found.

Installation

Install using yarn:

yarn add require-env-var

Install using npm:

npm install --save require-env-var

Usage

require-env-var exposes a single function:

const requireEnvVar = require('require-env-var');

const port = requireEnvVar('PORT');

You can also use ES6-style imports if you'd like:

import requireEnvVar from 'require-env-var';

const clientId = requireEnvVar('CLIENT_ID');

You can provide an array of keys and require-env-var will return the first one that is set:

const port = requireEnvVar(['SERVER_PORT', 'PORT']);

If none of the keys provided exist, require-env-var will throw an error:

Required environment variable [SERVER_PORT or PORT] is not set!

However, if you specify a fallback, that will be returned instead:

const port = requireEnvVar(['SERVER_PORT', 'PORT'], '8080');

console.log(port) // Suprise, it's `8080`!

License

MIT