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

@sabbatical/configure-local

v1.0.4

Published

Manage node.js instance environment configuration.

Downloads

16

Readme

configure-local

  • TypeScript 2.0 targeting es6
  • Node.js 6

Summary

This module wraps nconf, and provides a fixed policy of:

  • Use project local configuration files, in the ./config directory, to configure a node instance.
  • The configuration files match the name of the instance environment specified by the NODE_ENV environment variable.
  • Shared configuration is in common.json.
  • The precedence of the configuration sources is:
    • command line arguments
      Configuration settings passed on the command line override any other settings.
    • environment variables
      Configuration settings set in environment variables override any settings in configuration files.
    • the instance environment specific configuration file
      Configuration settings set in an environment specific configuration file override any settings in the common configuration file.
    • the common configuration file
      Configuration settings in the common configuration file are used when none of the other sources specify a setting.

Examples

See the tests

Usage

Assuming that you have three instance environments: development, qa, and production You would then have these files:

  • ./config/common.json
  • ./config/development.json
  • ./config/production.json
  • ./config/qa.json

To configure a module:

configure = require('@sabbatical/configure-local')

The configuration is loaded the first time configure-local is require'd.

To get the values of configuration parameters, use get() as in nconf:

configure.get()   // returns the entire configuration
configure.get('a:b')  // returns the value or object that would be accessed by ['a']['b']

To reload the configuration:

configure.reloadConfig()

Subsequent calls to configure.get will return updated values.

Setup for Build

npm install

Build

Build the software:

npm run build

Remove the generated files:

npm run clean

Test

Run the tests:

npm run test

Problems?

Please report them as issues on the GitHub repo.