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

strict-env

v1.1.0

Published

Enforce env vars for 12-factor apps in dev or prod

Downloads

1,455

Readme

strict-env

Enforce 12-factor app environment variables in development or production

NPM version NPM downloads Build status Coverage status

Recommended usage

  1. Create .env following dotenv formatting. Make sure to add it to your .gitignore file. Recommended to commit dummy values in a file example.env as well.
  2. npm i -E strict-env
  3. In config.js (or similar):
const env = require('strict-env');

/*
 * The `config` function expects a mapping of required environment
 * variables names to transformer functions. The library provides
 * transformers for common use cases, but you can easily provide
 * your own.
 */
module.exports = env.config({
  BOOLEAN: env.boolean, // Allows values: 'true', 'false', '1', '0'
  INTEGER: env.integer,
  JSON: env.json,       // Any valid input for `JSON.parse`
  NUMBER: env.number,
  PORT: env.port,
  STRING: env.string,   // Non-empty string

  /*
   * Custom transformers must either return the transformed value
   * or throw an error. They are invoked with two parameters:
   * value - String value of environment variable, or `undefined`
   *         if not set. (This allows you to specify variables that
   *         are optional or have default values.)
   * name - String name of the target environment variable. You
   *        sholud use this to generate nice error messages.
   */
  CUSTOM: (value, name) => {
    if (/\d+/.test(value)) {
      return Number(value);
    } else {
      const message =
        `Env. var. should be a non-negative integer: "${name}"`;
      throw new Error(message);
    }
  },
});

// You can also use the `get` function to process single variables.
// This is useful for ES modules!
export const PORT = env.get('PORT', env.port);
  1. Use config values in other files:
const config = require('./config');

console.info(config.CUSTOM); // Will be be a non-negative integer
console.info(config.PORT);   // Will be be a valid port number
console.info(config.STRING); // Will be be a non-empty string
// Etc.

// Or use ES modules
import { PORT } from './config';

Compatibility

This library should work with node versions as old as 0.10, thanks to Rollup and Babel. (Please file an issue if that is not the case!)