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

@learningalbum/env-validation

v1.1.1

Published

Validate environment config

Downloads

28

Readme

ENV validation library

This library is designed to support validating environment variables for a nodejs application of any kind.

How to use

In a file (e.g. config.js)

require('dotenv').config();

const {validate, validations, preProcessors} = require('@learningalbum/env-validation');

const {castBool} = preProcessors;
const {mustBeOneOf, requiredIfPresent, requiredIfTrue} = validations;

const varsConfig = [
  // Array of variable configs (see below)
  {
    name: 'MY_VAR',
    require: true,
  }
]

// Get the validated vars into an object like {VAR1, VAR2, VAR3, etc} 
module.exports = validate(varsConfig);

Then in your application code, wherever you need config from your env, you do stuff like:

const { MY_VAR } = require('config.js');
// Do something with MY_VAR

or, if using ESM:

import envs from './config.js';
const { MY_VAR } = envs;

If MY_VAR doesn't validate in the way you've configured in config.js, an error will be thrown with an error message describing why.

Variable configs

Declare each variable you want to validate. For full details on the interface, please see src/types.ts.

| key | type |required?| description | |-------------|--------------------------------------------------------|-|----------------------------------------------------------------------------------------------------------| | name | string |yes| the name of the variable to pick up from process.env | | default | any |no| a default value to use | | preProcess | (val: any) => any |no| function to transform the value before any validation | | validations | array of (val: any, context?: EnvContext) => boolean |no| function to validate the value | | deprecated | boolean |no| whether this var is marked as deprecated | | message | string |no| the deprecation message to show if the deprecated var is present (only relevant when deprecated: true) |