# nfs-config-resolver

> [![Build Status](https://travis-ci.org/nodeframe/config-resolver.svg?branch=master)](https://travis-ci.org/nodeframe/config-resolver) [![npm](https://img.shields.io/npm/v/nfs-config-resolver.svg)](https://www.npmjs.com/package/nfs-config-resolver)

Latest version **2.0.4** (published 2017-05-09) · ISC license · 0 weekly downloads

## Install

```sh
npm install nfs-config-resolver
pnpm add nfs-config-resolver
yarn add nfs-config-resolver
bun add nfs-config-resolver
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 2.0.4 |
| Published | 2017-05-09 |
| First published | 2016-11-21 |
| Weekly downloads | 0 |
| License | ISC |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 3 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 1 |
| Maintainers | nodeframe, puttpotsawee, southbridge |

## Links

- npm: https://www.npmjs.com/package/nfs-config-resolver
- Repository: https://github.com/nodeframe/config-resolver
- Homepage: https://github.com/nodeframe/config-resolver#readme
- Issues: https://github.com/nodeframe/config-resolver/issues
- npm.io page: https://npm.io/package/nfs-config-resolver

## Dependencies (3)

- [path](https://npm.io/package/path.md) ^0.12.7
- [parents](https://npm.io/package/parents.md) ^1.0.1
- [deepmerge](https://npm.io/package/deepmerge.md) ^1.3.0

## Recent versions

- 2.0.4 (latest) — 2017-05-09
- 2.0.3 — 2017-05-09
- 2.0.2 — 2017-01-20
- 2.0.1 — 2016-11-30
- 2.0.0 — 2016-11-30
- 1.2.2 — 2016-11-24
- 1.2.0 — 2016-11-24
- 1.0.5 — 2016-11-23
- 1.0.4 — 2016-11-23
- 1.0.3 — 2016-11-21
- 1.0.2 — 2016-11-21
- 1.0.1 — 2016-11-21
- 1.0.0 — 2016-11-21

## README

[![Build Status](https://travis-ci.org/nodeframe/config-resolver.svg?branch=master)](https://travis-ci.org/nodeframe/config-resolver) [![npm](https://img.shields.io/npm/v/nfs-config-resolver.svg)](https://www.npmjs.com/package/nfs-config-resolver)

# config-resolver

An environment base config resolver that will reduce your worries about config and environments! Have a development environment and the production where you need it to be different config? fine! config-resolver will solve it! Have a config you want to declare only once and share on all environments? fine! config-resolver got you covered!

## Installation
```sh
npm install nfs-config-resolver --save
```

## Usage Example

Create `configs` folder within your project directory

Create `common.js` `development.js` `production.js` files inside `configs` directory

```javscript
// common.js

module.exports = {
  "host":"localhost",
  "port":80
};

```

```javscript
// development.js

module.exports = {
  "port":81,
  "mongodb":{
    "host": "localhost"
    "port": "27017"
  },
  "mode": "admin"
};

```

```javscript
// production.js

module.exports = {
  "port":82
};

```

### How to use ###
You can override configuration with environment parameter

```javascript
// run with environment NODE_ENV=development MONGO_HOST=182.166.12.2 MODE=customer
const config = require('nfs-config-resolver')();

console.log(config)
/*
 {
  "port":81,
  "mongodb":{
    "host": "182.166.12.2"
    "port": "27017"
  },
  "mode": "customer"
}
*/
```

```javascript
// run with environment NODE_ENV = production
const config = require('nfs-config-resolver')();

console.log(config.port)
// 82
```

### ENV compatible

The great thing about this config-resolver is that it can help you on declaring config that needs to bind with the Environment Variables (eg. docker ENV)

You can declare you config by just adding `@` prefix and comma like so:

```javscript
// development.js

module.exports = {
  "port":81,
  "mongodb":{
    "@host:MONGODB_HOST": "localhost"
    "@port:MONGODB_PORT": "27017"
  },
  "@mode": "admin"
};

```

The config generated from this file will be as same as this config

```javscript
// development.js

module.exports = {
  "port":81,
  "mongodb":{
    "host": process.env.MONGODB_HOST || "localhost"
    "port": process.env.MONGODB_PORT || "27017"
  },
  "mode": process.env.MODE || "admin"
};

```

by this config, at runtime, the config value will be overwritten by the environment variable, wether it's linux or Docker. This allow you to have a cleaner setting and save your time on worrying and declaring those environments.

as from the example above, you can override the mongo host just by changing the environment variable at runtime, like this

    MONGODB_HOST=11.11.11.11 node ./index.js

and so on.

The most beneficial to this feature is those who make Docker image!

---
_Source: https://npm.io/package/nfs-config-resolver · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._