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 🙏

© 2025 – Pkg Stats / Ryan Hefner

turing-config

v0.50.0

Published

Hierarchical configuration with files, environment variables and command-line arguments.

Downloads

59

Readme

turing-config

version license

Hierarchical configuration with files, environment variables and command-line arguments.

API

turing-config will merge configs from several sources into one config. Therefore it will override configs from following sources from default (1) to strongest (3):

  1. env variables
  2. default config
  3. process.env.ACTIVE_PROFILE specific config

The default config sets the base, ACTIVE_PROFILE specific config overrules default config and env variable config overrules everything.

Only the env variables specified in custom_env file will be merged into config.

Config Dir

The default config dir will be /config. To change that set the TURING_CONFIG_DIR env variable.

Default Config

Default configs are stored in a default.json file inside your config dir.

ACTIVE_PROFILE specific config

To add ACTIVE_PROFILE specific configs add a config file called {ACTIVE_PROFILE}.json to the config dir.

Env Variables

To add config values from env variables you have to create a file called custom_env.json.

get(configPath)

To get a config value simple require turing-config and call get(configPath) inside the config dir.

const config = require('turing-config');

const myConfigPathValue = config.get('my:config:path');

Contributors

  • Benedikt Stemmildt
  • Jonathan Meyer

License

Apache-2.0