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

@pitininja/envious

v4.1.4

Published

> Environment variable parsing using Dotenv & Typebox

Downloads

901

Readme

Envious

Environment variable parsing using Dotenv & Typebox

Install

npm i @pitininja/envious

Usage

Environment variables are automatically loaded using Dotenv.

Refer to the official Typebox documentation for how to write a Typebox schema.

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

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

Formats

String formats can be loaded in the formats property of the options parameter, as an object with the format name as key and a regex or a validation function as value.

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

const env = envious(
    Type.Object({
        EXAMPLE_URI: Type.String({ format: 'uri' }),
        EXAMPLE_DATE: Type.String({ format: 'date' })
    }),
    {
        formats: {
            uri: /^(?:[a-z][a-z0-9+\-.]*:)(?:\/?\/)?[^\s]*$/i,
            date: (val) => dayjs(val).isValid()
        }
    }
);

Errors

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

An EnviousError error contains a message and a list of ValueError (an error class taken from Typebox).

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

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

try {
    const env = envious(
        Type.Object({
            STRING_VAR: Type.String()
        })
    );
} catch (err: unknown) {
    if (err instanceof EnviousError) {
        console.log('Message:', err.message); // Error message
        console.log('Errors:', err.errors); // Typebox's ValueError array
    }
}