New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Take parser out in a separate project #245
Comments
Closing as a dupe of #181 Note that |
@tamtakoe If you prefer exactly how node-config does this over node-rechoir, you are welcome to put the open source license to use and copy the code into a module of your own that you document and publish. Let us know if you get that far, then we'll have an alternative to |
Why do not you use this
How to disable these warnings? |
Regarding Regarding the warning, see https://github.com/lorenwest/node-config/wiki/Environment-Variables#suppress_no_config_warning Also, searching for the warning in the source code would have quickly found the environment variable used to surpress it. Further conversation about splitting out the config file loading / parsing can happen in #181 if you are interested. |
I hide warnings, thank! I think I put +1 in #181 :-) |
Take
parseString
out in a separate git/npm project, pleaseThe text was updated successfully, but these errors were encountered: