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

check-environment

v0.1.0

Published

A module to check environment variables against a predefined yaml config

Downloads

2

Readme

check-environment

Build Status Known Vulnerabilities

Description

This is a node.js module that will check currently set environment variables against a pre-defined specification.

Getting started

install using npm:

  • npm i -S check-environment

Add your env.yaml at the same level as your package.json and call this module at the top of the entrypoint to your app (i.e. app.js or index.js), like below;

const envCheck = require('check-environment')();

An example of a configuration file can be seen below;

---
NODE_ENV:
  required: true
  type: string
  format: "^(development|test|production)$"
  log: true

Documentation

Environment variable specification

Under the key of the name of the environment variable, an object with the following parameters:

| Param | Type | Default | Description | | ---------------------- | ------------- | ------- | --------------------------------------------------------------------------------------------- | | required | boolean | false | whether or not to auto-load the spec | | type | string | "any" | either 'boolean', 'string', 'number or 'any' | | format | string | none | a RegExp pattern string to use to validate the environment variable | | | or object | none | specifying a RegExp pattern and modifiers in an object | | format.pattern | string | none | a RegExp pattern string to use to validate the environment variable | | format.flags | string | none | a string containing a combination of: m, i, and/or g to use as part of the validation pattern |

Module: (options (optional)) ⇒ Checker

Creates and returns an instance of a Checker passing in the user supplied configuration options Name: none (module's sole export) Kind: function (synchronous)

Parameters

| Param | Type | Default | Description | | ------------------------ | --------- | ------- | ----------------------------------------------- | | options | object | n/a | configuration object | | options.autoLoad | boolean | | whether or not to auto-load the spec | | options.specLocation | string | | the location of the environment specification |

Returns: an instance of Checker

Checker

Property: specLocation

Type: String Description: the location of the environment specification (Can be YAML or JSON)

Method: loadSpec()

Description: Loads the specification and checks it's validity.
NOTES:

  • automatically run on instantiation if autoLoad is not set to true

Method: check() => Object

Description: Checks environment variables against Returns: An object with keys equal to the names of set and valid environment variables, and their values converted to their specified type.
NOTE:

  • Requires loadSpec() to have been run first
  • automatically run on instantiation if autoLoad is not set to true