New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

require-env-var

Package Overview
Dependencies
Maintainers
1
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

require-env-var

Easily require environment variables or else

  • 0.1.3
  • latest
  • npm
  • Socket score

Version published
Maintainers
1
Created
Source

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

Keywords

FAQs

Package last updated on 03 Sep 2021

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc