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

confi

v10.0.1

Published

a simple configuration library

Downloads

159

Readme

Confi loads configuration data from yaml, json or from a package.json with support for NODE_ENV overrides.

Installation

npm install confi

or

yarn add confi

Usage

Note: confi() is an async method.

Note: Default configuration directory is ./conf/

Configuration files that start with default are loaded and merged together. This allows you to split up configuration logic into smaller files.

You can create a file that matches NODE_ENV which will apply it's values on top of anything set in default. This allows you to create configuration for production and development environments.

User specific configuration can be created as well by placing config files in a users directory inside of the config directory.

./conf/default.yaml

title: 'Example Site'
site:
  name: '{{ title }} - DEV'
updateEvery: '{{ ms("1h") }}
appId: '{{ getEnv("APP_ID", '09830948029384') }}'
shot: false

./conf/users/han.json

{
  "shot": true
}

./conf/production.yaml

site:
  name: '{{ title }}'
updateEvery: '{{ getEnv("UPDATE_EVERY", ms("1h")) }}'

Basic

const confi = require('confi');

async function startApp() {
  const config = await confi();

  console.log(config.site.name); // Example Site - DEV
  console.log(config.appId); // 09830948029384
  console.log(config.updateEvery); // 3600000
  console.log(config.shot); // false
}

startApp();

User

const confi = require('confi');

async function startApp() {
  const config = await confi({
    user: 'han'
  });

  console.log(config.site.name); // Example Site - DEV
  console.log(config.appId); // 09830948029384
  console.log(config.updateEvery); // 3600000
  console.log(config.shot); // true
}

startApp();

Environment

// imagine process.env.UPDATE_EVERY is 10000
const confi = require('confi');

async function startApp() {
  const config = await confi({
    env: 'production'
  });

  console.log(config.site.name); // Example Site
  console.log(config.appId); // 09830948029384
  console.log(config.updateEvery); // 10000
  console.log(config.shot); // true
}

startApp();

For more examples, see the test directory.

Options

confi([options])

  • path - Supply an alternate path to load config from. Default: process.env.CONFI_PATH or ./conf
  • env - Manually set the envitonment. Default: dev
  • userPath - Path for user overrides. Default: ./conf/users
  • context - Advanced option to pass additional information to varson for parsing configs.
  • helpers - Additional helper methods to expose.
  • user - Which user shall the user config be loaded for.

Helpers

Confi comes with a set of helper methods. You can find documentation for them here.


A First + Third Project