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

envboss

v1.1.1

Published

package for environment variables

Downloads

109

Readme

Known Vulnerabilities Build Status Coverage Status GitHub npm (scoped)

EnvBoss

Tired of using process.env everywhere in the code? Tired of guessing which environment variable are mandatory and which are optional? Tired of validating environment params?

meet EnvBoss!!!

This package will help you organize and validate all your environment variables in one place.

Installation

> npm i envboss

How to use

/// envVariablesConfig.js

import { createEnvObject, mandatory, Types } from 'envboss';

const ENV_VARS_CONFIG = {
    CLUSTER: { mandatory: true },
    ENVIRONMENT: { mandatory, validValues: ['live', 'sandbox']},
    IS_MASTER: { mandatory, type: Types.Boolean },
    IP_ADDRESSES_ARR: { mandatory, type: Types.Array }, //resolves as array of ip addresses
    STORAGE_PORT: { mandatory, wrappingFunction: someFunc },

    // optional
    PORT: { default: 8082 },
    PROCESSOR_TIMEOUT: { default: 50000},
    RETRY_TIMES: { default: 10, validationFunction: (v) => v > 3},
    LOG_LEVEL: { default: 'info' }
};

module.exports = createEnvObject(ENV_VARS_CONFIG);
/// someFile.js
const { ENVIRONMENT } = require('envVariavbesConfig.js');

How does it work?

It goes over the configuration you provide, and returns an object where the key is the <ENV_PARAM_NAME> and the value is process.env[<ENV_PARAM_NAME>] after it was validated and sanitized.

configuration

mandatory - when set to true, sets this param as mandatory. Can be used as mandatory only when required from 'envboss';

default - lets you define a default value.

type - converts the given envParam value from 'string' to given Type. Supported types: Number, Boolean, String, Array. By default, if default config is provided, process.env[<ENV_PARAM_NAME>] value will be converted to the type default's value type

validationFunction - will help you validate the values.

validValues- lets you describe what values are valid.

wrappingFunction - converts the envparam value to the given value.

If you wouldn't like to validate envparams (e.g. in tests) pass false to createEnvObject(ENV_VARS_CONFIG,false)