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

eu-node-config

v0.0.4

Published

A simple config file loader

Downloads

3

Readme

EuNodeConfig

NOTE, THIS IS A WORK IN PROGRESS AND NOT COMPLETE AT THIS TIME To see what works, look at the test(s).

Node config is a simple library for loading configuration from the environment and various file formats. It allows your users to specify their configs in various formats and takes care of parsing the formats appropriately for you.

Usage

This module exports only one function: loadConfig.

var configLoader = require('eu-node-config');
configLoader.loadConfig({
  username: {
    default: "bob", // A config with a default value can't be required
  },
  username2: "anotherDefaultFormat",
  secure: {
    required: true,
    error: "Missing required config value: secure" // This default message will be printed if you do not supply your own. This can only be used if the config has a validation, such as required.
  },
  anotherConfigKey: {
    error: true
  },
  finalConfigKey: {} // This config value will not be required and might not be in the object returned
}, {
  configFolders: ['/etc/myconf'],                       // Optional, defaults to working directory and then process base directory
  filePrefix: 'part-before-the-dot',                    // Optional, defaults to config
  order: ["string", "environment", "json", "yaml", "defaults"], // Optional, defaults to the value shown left; earlier values will override later values
                                                        // other options include "js" to load from a .js file
  configString: '{"key": "value"}',                     // The 'string' source above.
}, function(err, config) {
  console.log("Config loaded: " + config);
});

// Alternately, promise style
configLoader.loadConfig({username: {default: "bob"}, {jsonData: '{"username":"bill"}'})
.then(function(config) {
  console.log(Config loaded: " + config);
})
.error(function(err) {
  console.log("Failed to load config: " + err);
});

Formats supported

.yaml, .json, and .js

From the above description, your config will be loaded from a file if it begins with your filePrefix (default config) and ends with ".json" or ".yaml". If you enable "loadJsConfigs" it will also load .js extension files.

Environment variables

Environment variables matching either your config key or your config key converted to upper-case and with camelcasing normalized to underscore seperation will be used.

For example, the config key "configKey" will be accessed as either the environment variable "configKey" or "CONFIG_KEY"