config-ninja
Advanced tools
Comparing version 0.0.7 to 0.0.8
@@ -22,3 +22,3 @@ /* | ||
dir = ME._cfgPath; | ||
if (typeof env === 'undefined') { env = ME._env; } | ||
if (!env) { env = ME._env; } | ||
} | ||
@@ -32,3 +32,3 @@ | ||
// Get the enviroment. | ||
if (typeof env === 'undefined') { env = process.env.NODE_ENV || 'development'; } | ||
if (!env) { env = process.env.NODE_ENV || 'development'; } | ||
@@ -35,0 +35,0 @@ // Load the environment config? |
@@ -13,3 +13,3 @@ { | ||
"name": "config-ninja", | ||
"version": "0.0.7", | ||
"version": "0.0.8", | ||
"description": "Environmental JSON config.", | ||
@@ -16,0 +16,0 @@ "keywords": [ |
@@ -26,2 +26,7 @@ # Config-Ninja | ||
## Specify Options | ||
You can also specify some options when instantiating Config-Ninja. All options are optional. | ||
* **configInFilename** `true` Set false if you want to your config filenames to be in the format of "development.json" instead of the default "development.config.json". | ||
## Setup Config Files | ||
@@ -28,0 +33,0 @@ Typically you will need 2 config files, one for `production` and one for `development`. You may also want config files for other enviroments such as `staging`. |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
5326
55