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

apprc

v2.0.3

Published

opinionated and non-configurable config loader for lazy people who like yaml

Downloads

20

Readme

apprc

build status npm version npm downloads npm dependencies

My opinionated and almost-non-configurable configuration loader for lazy people who like yaml.

  • 1 file for multible environments
  • supports yaml or json
  • deep-freezes config object

Installation

yarn add apprc

Usage

apprc will look for config files in the following locations:

  • closest .${appName}rc by continuously looking in '../' until '/' is reached
  • $HOME/.${appName}rc
  • $HOME/${appName}/config
  • $HOME/.${appName}/config
  • $HOME/.config/${appName}rc
  • $HOME/.config/${appName}/config
  • /etc/${appName}rc
  • /etc/${appName}/config

files can optionally have the .yml or .json extension in their names

Module

const config = require('apprc')(defaults, envKey, appName)

arguments default to:

defaults = {}
appName = package_json.name
envKey = process.env.NODE_ENV || 'development'

CLI

$ apprc --help

apprc <variable> [args]

Options:
  --env, -e        Environment                               [string] [required]
  --name, -n       Name (default: "name" in package.json)               [string]
  --force, -f      Don't bail on missing value                         [boolean]
  --undefined, -u  Fallback output of missing value                     [string]
  --delimiter, -d  Custom path delimiter (default: ".")  [string] [default: "."]
  --help, -h, -?   Show help                                           [boolean]


$ apprc --env production
{"http":{"port":80}}

$ apprc http --env production
{"port":80}

$ apprc http.port --env production
80

Config Format

Config files must be in the JSON or YAML format:

---
defaults:
    view_engine: jade

development:
    http_port: 8080

production:
    http_port: 80

loaded with:

const config = require('apprc')('development')

results in:

{
    "view_engine": "jade",
    "http_port": 8080
}

LICENSE

MIT