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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@pitininja/envious

v6.1.5

Published

[![npm version](https://badge.fury.io/js/@pitininja%2Fenvious.svg)](https://badge.fury.io/js/@pitininja%2Fenvious)

Readme

Envious

npm version

Parse and validate environment variables

Install

Envious works by installing and using two packages : the core package and a resolver.

Core package

npm i @pitininja/envious

Resolvers

Typebox

npm i @pitininja/envious-typebox

Yup

npm i @pitininja/envious-yup

Zod

npm i @pitininja/envious-zod

Usage

Here is an example using the Typebox resolver :

import { envious } from '@pitininja/envious';
import { typeboxResolver } from '@pitininja/envious-typebox';
import { Type } from '@sinclair/typebox';

const env = envious({
    resolver: typeboxResolver({
        schema: Type.Object({
            STRING_VAR: Type.String(),
            NUMBER_VAR: Type.Integer(),
            BOOLEAN_VAR_WITH_DEFAULT: Type.Boolean({ default: false }),
            OPTIONAL_VAR: Type.Optional(Type.String())
        })
    })
});

Then run the script with loaded environment variables, and these variables will be parsed and validated.

# Example loading environment variables with Node.js
node --env-file=.env index.js
# Example loading environment variables with TSX
tsx --env-file=.env index.ts
# Example loading environment variables with DotEnv
dotenv -e .env -- node index.js

Options

Logging

In addition to throwing an EnviousError, errors can be logged in the console. To do so, use the logErrors option :

import { envious } from '@pitininja/envious';
import { typeboxResolver } from '@pitininja/envious-typebox';
import { Type } from '@sinclair/typebox';

const env = envious({
    resolver: typeboxResolver({
        schema: Type.Object({
            STRING_VAR: Type.String()
        })
    }),
    logErrors: true
});

You can also provide your own logging function :

import { envious } from '@pitininja/envious';
import { typeboxResolver } from '@pitininja/envious-typebox';
import { Type } from '@sinclair/typebox';

const env = envious({
    resolver: typeboxResolver({
        schema: Type.Object({
            STRING_VAR: Type.String()
        })
    }),
    logErrors: true,
    logger: (message) => {
        myCustomLogger(message)
    }
});

Errors

If something goes wrong, Envious will throw an error of class EnviousError.

An EnviousError error contains a message and a list of EnviousErrorVariable.

Here is a simple example of how to handle Envious errors :

import { envious, EnviousError } from '@pitininja/envious';
import { typeboxResolver } from '@pitininja/envious-typebox';
import { Type } from '@sinclair/typebox';

try {
    const env = envious({
        resolver: typeboxResolver({
            schema: Type.Object({
                STRING_VAR: Type.String()
            })
        })
    });
} catch (err: unknown) {
    if (err instanceof EnviousError) {
        // General error message
        console.log('Message:', err.message);
        // Array of EnviousErrorVariable
        console.log('Errors:', err.errors);
        for (const { name, messages } of err.errors) {
            // Variable name and error messages related to that variable
            console.log(`${name} : ${messages.join(', ')}`);
        }
    }
}

Migration

Migration guide to v6

Legacy versions

Legacy documentation for v5 or lower