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

@gradebook/config

v0.1.0

Published

> Opinionated config loader for nconf. Based on @tryghost/config

Downloads

21

Readme

@gradebook/config

Opinionated config loader for nconf. Based on @tryghost/config

Usage

import {getConfig, coerceKeyToBoolean, coerceToBoolean} from '@gradebook/config'

export const config = await getConfig(/* environmentOverride */);

// Works just like nconf
console.log(config.get('env')); // 'development' if no overrides are set

// Also supports forcing boolean types
coerceKeyToBoolean(config, 'featureFlag:feature');
// Which is really just
config.set('featureFlag:feature', coerceToBoolean(config.get('featureFlag:feature')));

// true | false (boolean)
console.log(config.get('featureFlag:feature'));

Configuration

The config loader looks for 2 files - config.example.json (defaults), and config.{env}.json (env).

  • If you provide the GB_CONFIG_ROOT env variable, the config loader will look for the default and env configs in this folder.

  • If there is no GB_CONFIG_ROOT, the config loader will walk up process.cwd() until it finds a defaults file.

  • The env is picked from (in order):

    1. The environmentOverride param from the getConfig call
    2. process.env.NODE_ENV
    3. development (default)

Typing

Since the config is not validated, there is no guarantee that a specific key will exist / be the expected type.