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

@livingdocs/conf

v3.0.2

Published

Package to load, merge and access environment-specific configuration files.

Downloads

5,652

Readme

@livingdocs/conf

Greenkeeper badge

Package to load, merge and access environment-specific configuration files.

How to use

Example how to load the configuration for an environment defined in an environment variable:

const path = require('path')
const Conf = require('@livingdocs/conf')

const appConf = Conf.loadEnvironment(path.resolve('./conf'), process.env.ENVIRONMENT)

Required folder structure

This modules assumes a specific folder structure. Following is an example:

yourConfigFolder/
  environments/
    all.js
    local.js
    staging.js
    production.js
  secrets/
    local.js

To load a e.g the 'local' environment use loadEnvironment(path.resolve('./yourConfigFolder'), 'local').

This will go through the following steps:

  1. load environments/all.js
  2. merge environments/local.js
  3. merge secrets/local.js
  4. merge environment variables

The environment names local, staging, production are not defined. You can use whatever you want there.

#### Environment variables

Example all.js:

db: {
  database: 'foo'
}

You can override the database property as follows:

exports db__database=bar

Double underscores (__) denote a child property.

API

The loadEnvironment method is the main entry point to init a configuration.

const appConf = Conf.loadEnvironment(file, environment)

Get a config value. Note: this will throw an error if the config is not present.

appConf.get('db:database')

To safely query for a config value provide a default value as the second param.

appConf.get('db:database', null)

You can also set config values programmatically:

appConf.set('db:database', 'bar')

You can manually merge whole objects to set configs in bulk:

appConf.merge(obj)

Outputs the whole configuration as json string:

appConf.toString(obj)

Copyright

Copyright (c) 2015 Livingdocs AG, all rights reserved

It is not permitted to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of this Software, except when explicitly stated otherwise by Livingdocs AG.