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

outfield

v0.2.1

Published

Async configuration loader/validator built on top of shortstop

Downloads

7

Readme

outfield

Async configuration loader/validator built on top of shortstop

Usage

var joi = require('joi'); // used for validations

var config = require('outfield');

var schema = {
  DATABASE_URL: {
    description: 'The connection string for the Database',
    validate: joi.string().uri(),
    default: 'postgres://postgres@localhost:5432/testdb'
  }
};

config(schema, function(err, env){
  // err if validation or resolution fails

  env.DATABASE_URL; // 'postgres://postgres@localhost:5432/testdb'
});

API

config(schema, [options], callback)

The only method. Takes a schema object, optional options, and a callback. The schema is parsed, resolved, populated and validated and the callback is called with an error or an object containing the environment. Everything is resolved using the process.env with fallbacks to resolving the resolve property using shortstop and then the default property.

schema

The schema object is composed of keys for your environment. Each key is assigned a definition object comprised of 4 keywords. Instead of a definiton object, you can nest keys; However, if there are any keywords, the nesting will be ignored.

  • description (optional) - Used to describe your configuration. Not currently used internally, but allows for extra features in the future.
  • validate (required) - Used to validate and convert values to proper types. Accepts joi validations.
  • default (optional) - Used to provide a default to your environment if the key can't be resolved or isn't in process.env.
  • resolve (optional) - String that resolves to a registered shortstop handler. Note: No shortstop handlers are registered by default. They must be added using the options object.

options

The options object allows you to register shortstop handlers and adjust joi configuration.

  • handlers (optional) - Object containing key/handler pairs of shortstop handlers to register in the shortstop instance. The handler can be an array of handlers, each will be registered as the key.
  • joi (optional) - Object containing joi configuration overrides. Note: In this module, allowUnknown is defaulted to true, abortEarly is defaulted to false and presence is defaulted to required instead of the joi defaults.

callback(err, env)

The callback function is called once all resolution and validation is done. If resolution or validation fails, the callback will be called with an error. If everything succeeds, the env argument will be an object containing the fully resolved environment. Also, the property NODE_ENV will be resolved to development if undefined in the environment and the properties development, production, test and staging will be resolved to booleans based on NODE_ENV. Note: environment variables will not be resolved if allowUnknown is false in the joi configuration.

License

MIT