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

@hzabala/envconfig

v0.1.1

Published

An env config validator using [JSON schema](https://json-schema.org/)

Downloads

2

Readme

envconfig

An env config validator using JSON schema

Installation

Install latest using npm:

npm install @hzabala/envconfig

Usage

You can start by creating an interface to structure your config and provide it as type to JSONSchemaType<T>. Define your schema as you would normally do using JSON Schema, but type should always be object and additionalProperties to true (especially when you're using dotenv).

Pass process.env (if you're using dotenv) or any key-value pair to the function as input.

import { JSONSchemaType } from 'ajv';
import dotenv from 'dotenv';
dotenv.config();

import { createConfig } from '@hzabala/envconfig';

interface Config {
  PORT: number;
  DATABASE_URL: string;
  SECRET: string;
}

const schema: JSONSchemaType<Config> = {
  type: 'object',
  properties: {
    PORT: {
      type: 'integer',
      default: 3000,
    },
    DATABASE_URL: {
      type: 'string',
    },
    SECRET: {
      type: 'string',
    }
  },
  additionalProperties: true,
  required: ['DATABASE_URL', 'SECRET']
}

const config: Config = createConfig({ input: process.env, schema });

This project uses Ajv and supports Ajv-formats and Ajv-keywords out of the box.

If you want to use additional Ajv plugins then you can extend the Ajv instance:

import addErrors from 'ajv-errors';
import { createConfig, AjvInstance } from '@hzabala/envconfig';

addErrors(AjvInstance);

You can also override the instance by passing your own, but this would remove the defaults:

const ajvInstance = new Ajv();
const config: Config = createConfig({ input: process.env, schema }, ajvInstance});

See Examples

Custom Keywords

splitter

Configs can have array as value usually separated by commas. You configure that using the splitter keyword:

# .env
VALUE=one,two,three,four
// example.ts
import { JSONSchemaType } from 'ajv';
import dotenv from 'dotenv';
dotenv.config();

import { createConfig } from '@hzabala/envconfig';

interface Config {
  VALUES: string[];
}

//@ts-ignore
const schema: JSONSchemaType<Config> = {
  type: 'object',
  properties: {
    VALUES: {
      type: 'string',
      splitter: ','
    },
  },
  additionalProperties: true,
  required: ['VALUES'],
}

const config: Config = createConfig({ input: procecss.env, schema });
// ['one','two','three','four']

This only supports string and you also need to suppress the error with //@ts-ignore because typescript tries to match the types in the interface and in the schema and we don't have a fix for that now.

Contributing

Pull requests are welcome. Please open an issue first to discuss what you would like to change.

License

MIT License

Copyright (c) 2021 Heanzy Zabala

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.