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

required-env-var-plugin

v1.0.0-beta.1

Published

Webpack plugin for enforcing environmental variables.

Downloads

1

Readme

#required-env-var-plugin Build Status

Require an environmental variable in your application or throw routhlessly.

A zero-dependency webpack plugin.

##Motivation

If you have ever found yourself setting up default env vars in your project just to make sure your app does get some data when a developer forgets to provide it, you run a risk of serving a hard debugging time to other contributors or even worse, ending up with wrong configuration in deployment process.

No more accidental values for environmental variables in your app. Get a hard reminder on your face that there's something to be set.

##Usage

The only requirement is a webpack package installed, but since you're checking out a webpack plugin, you're probably already there.

Just register the plugin and provide the required env var names as parameters:

const RequiredEnvVarPlugin = require('required-env-var-plugin')
//...
module.exports = {
  //...
  plugins: [
    new RequiredEnvVarPlugin('API_URL', 'USER', 'PASS')
  ]
  //...
}

You can provide the variables both as a list: REVP('API_URL', 'USER', 'PASS') or as an array: REVP(['API_URL', 'USER', 'PASS']).

#How does it work?

Under the hood it just uses webpack's DefinePlugin and passes it the object of shape:

{
  'process.env': {
    API_URL: xxx,
    USER: xxx,
    PASS: xxx,
  }
}

where xxx are respective environmental variables derived from process.env.xxx. If it doesn't find one, throws.

##FAQ

###Why throw? Can't I just warn the user?

No. That's the whole purpose of the plugin. If developer didn't infere from the code, didn't find out from the docs or didn't deduce from the application working that the env var hadn't been set, then he surely won't notice it in a bunch of logs spitted onto the console during startup. The message has to be clear: You forgot to do it, I won't launch!

License

MIT (https://opensource.org/licenses/mit-license.php)