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

@comodinx/config

v0.0.3

Published

@comodinx/config is a Node.js configuration helper.

Downloads

5

Readme

Config

@comodinx/config is a Node.js configuration helper.

Index

Download & Install

NPM

    npm install @comodinx/config

Source code

$ git clone https://gitlab.com/comodinx/config.git
$ cd config
$ npm install

How is it used?

  • Static.
  • Extensible.
  • Configurable by environment.
  • Try a function to automatically require all files and folders recursively, keeping the naming structure.

Configure

Environment options

| Environment variable | Value | Default value | Description | |:-------------------------|:--------------|:--------------|:---------------------------------------------------------------------------------------------| | CONFIG_SEPARATOR | string | "."`` | Indicate config key separator. | | CONFIG_PRIVATE | boolean | false | Indicate if config object has raw property. | | CONFIG_EXTRA_ENVIRONMENT | boolean |false | Indicates that in addition to loading the.envfile, the.env.{NODE_ENV}` will be loaded. |

Folder structure

 <My config folder name>
 |
 | -> index.js
 |    // Content: `module.exports = require('@comodinx/config').require(module, __dirname);`
 |
 | -> server.js
 |    // Example server file: `module.exports = { port: 8080 };`
 | -> my-config-file.js
 |    // Other example config file: `module.exports = { key: value, a: 'b', c: 1 };`
 | -> ...
 |
 | -> my-config-folder
 |     | -> types.js
 |          // Other example config file anidate: `module.exports = { 1: 'immediate', 2: 'periodic', 3: 'scheduled' };`
 |     | -> ...
 |
 | -> production
 |     | -> types.js
 |          // Override types for production environment.
 |     | -> ...
const config = require('@comodinx/config');

// Simple usage
config('server.port'); // return: port value
config('my.not.exist.config'); // return: undefined
config('my.not.exist.config', 'my-default-value'); // return: 'my-default-value'

// Extend with object
config.extend({
  my: {
    config: {
      object: {
        hello: 'world!'
      }
    }
  }
});
config('my.config.object.hello'); // return: 'world!'
config('my.config.object'); // return: { hello: 'world!' }
config('my.config'); // return: { object: { hello: 'world!' } }

// Require all files on current folder
config.require(module, __dirname);
// Require all files on other folder
config.require(module, './my/other/folder');
// See more options on https://www.npmjs.com/package/require-directory#options
config.require(module, __dirname, {
  // Blacklist
  exclude: /dontinclude\.js$/,
  // Rename keys
  rename: name => name.toUpperCase()
});

Example when CONFIG_EXTRA_ENVIRONMENT is enabled

Example project folder structure

 <root>
 |
 | -> config
 |    // Content: all configuration files
 |
 | -> index.js
 |    // Content: project main source code

config folder

 config
 |
 | -> index.js
 |    // Content: `module.exports = require('@comodinx/config').require(module, __dirname);`
 |
 | -> server.js
 |    // Example server file: `module.exports = { port: process.env.SERVER_PORT, host: process.env.SERVER_HOST };`

.env file (on project root)

NODE_ENV=local
SERVER_PORT=8001
SERVER_HOST=localhost
CONFIG_EXTRA_ENVIRONMENT=true

.env.local file (on project root)

NODE_ENV=local
SERVER_PORT=8080

index.js main source code (on project root)

const config = require('./config');

// Simple usage
config('server.port'); // return: 8080
config('server.host'); // return: localhost

Tests

In order to see more concrete examples, I INVITE YOU TO LOOK AT THE TESTS :)

Run the unit tests

npm test