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

ini-config

v0.1.1

Published

main.ini + env.ini config

Downloads

18

Readme

ini-config

OOTB solution for constructing a config array from main and environment INI files.

What you get

In your project root directory:

config/main.ini        # non-environment-specific settings
config/env.ini         # local settings, ignored by git
config/env.example.ini # optional example of env.ini
config/.gitignore

In your app:

// an array of merged settings
var config = require('ini-config');

// for test environment you can override settings using a specific section
config.apply('test');

Installation

$ npm install ini-config --save

Configuration

  1. Create config folder in your project root directory:
$ mkdir config
  1. Create 2 ini files:
$ touch config/main.ini
$ touch config/env.ini
  1. Ignore env.ini file:
$ echo 'env.ini' > config/.gitignore
  1. Add default and non-environment-specific settings into main.ini.
;example
[web]
host = localhost
port = 3000
[mongodb]
connectionString = mongodb://localhost:27017/app
  1. Add settings for the current environment into env.ini.
;example
[web]
port = 3008
[mongodb]
connectionString = mongodb://user:password@dbhost:27017/app
  1. Optionally, you can save an example of env.ini as env.example.ini.

Usage

var config = require('ini-config');

console.log(config.web.host);  // get string parameter
console.log(+config.web.port); // get int parameter
console.log(config.mongodb);   // get section

Settings from env.ini will override settings from main.ini.

Test Environment

In order to keep logic simple and straightforward, there is no option for using different INI files. Instead, you can specify changes for test environment in env.ini under section test:

[test.web]
port = 3008

[test.mongodb]
connectionString = mongodb://localhost:27017/test

Apply changes before running tests:

var config = require('ini-config');
config.apply('test');

Note: Do not use section "apply" in INI files, a function will replace it.