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

polyconfig

v1.0.4

Published

a polyglot configuration library

Downloads

760

Readme

PolyConfig

A polyglot configuration library for node.js

Bored of writing the same configuration code over and over again? PolyConfig is here to help! you can use it to load configuration from various sources and mix them together with a priority order.

Deep dive

.env

API_SERVER_PORT=8080
API_SERVER_HEADERS_X-POWERED-BY=Env-Mummy

api.yaml

server:
  headers:
    x-powered-by: Yaml-Daddy
  ping_response: up

index.js

const poly = PolyConfig()
    .from('yaml', 1, { path: './api.yaml' }) // load from yaml file with priority of 1 (highest)
    .from('env', 2, { prefix: 'API' }) // load from environment variables with priority of 2 (lower)
    .require('server.port', Number) // set your first required var, require will throw if not found
    .optional('server.headers.x-powered-by', String, 'Default-Granny') // you can set optional vars with default values
    .optional('server.ping_response', (value: any) => (['up', 'down'].includes(value) ? value : 'down')) // and you can also set custom validator function ;)
let fullConfig = poly.get(); // access the full config object
let serverPort = poly.get('server.port'); // or to a specific value
let serverConfig = poly.get('server'); // or to a sub-object

console.log(fullConfig);
// {
//     server: {
//         port: 8080,
//         headers: {
//             'x-powered-by': 'Yaml-Daddy'
//         },
//         ping_response: 'up'
//     }
// }