Installations
npm install mcms-node-config-loader
Developer Guide
Typescript
No
Module System
N/A
Node Version
0.12.7
NPM Version
2.11.3
Score
66.9
Supply Chain
75.7
Quality
74.9
Maintenance
25
Vulnerability
100
License
Releases
Unable to fetch releases
Contributors
Unable to fetch Contributors
Languages
JavaScript (100%)
Love this project? Help keep it running — sponsor us today! 🚀
Developer
mbouclas
Download Statistics
Total Downloads
2,784
Last Day
1
Last Week
7
Last Month
35
Last Year
168
GitHub Statistics
6 Commits
3 Watching
1 Branches
1 Contributors
Bundle Size
56.02 kB
Minified
20.30 kB
Minified + Gzipped
Package Meta Information
Latest Version
0.0.4
Package Id
mcms-node-config-loader@0.0.4
Size
2.87 kB
NPM Version
2.11.3
Node Version
0.12.7
Total Downloads
Cumulative downloads
Total Downloads
2,784
Last day
0%
1
Compared to previous day
Last week
-22.2%
7
Compared to previous week
Last month
483.3%
35
Compared to previous month
Last year
32.3%
168
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
mcms-node-config-loader
Easily load config files for multiple environments
What does it do
This packages allows you to easily load the right config file depending on the environment you're working on
Install
npm install mcms-node-config-loader
Folder structure
The library expects a structure like so :
/configDir
/devEnv
configFile.json
/anotherEnv
configFile.json
configFile.json
anotherConfigFile.json
Every file under the configDir is loaded as production environment. If you create a subdirectory named after an environment you have defined before calling the module, it will overwrite the default config. For example, you have a mysql.json config under the configDir with your mySQL connection settings. If you create the same file with different settings under the configDir/development directory, when you're working on your dev machine theses settings will be loaded instead
Usage
check the examples folder for usage scenarios Initialize like so :
var path = require("path");
var environments = {
'development' : ['ubuntu','mike-PC','mint-box'],
'production' : 'myProductionBox'
};
var configLoader = require("../index").setEnv(environments);
var Config = configLoader.loadConfig(path.join(__dirname,'./config'));
That's it, under the Config object you can now access all your settings
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/6 approved changesets -- score normalized to 0
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Score
3
/10
Last Scanned on 2025-02-03
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More