-
Notifications
You must be signed in to change notification settings - Fork 499
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
how can i suppress "NODE_ENV value of 'test' did not match any deployment config file names." warnings? #386
Comments
The answer is on the linked web page, under the section about the specific warning you got. |
you mean creating a file for it to find? i understand that would stop the warning. i wanted to know if there was a way to simply suppress it's display. if there's not, ok, there's not. it's a library though so not sure i'll always have control of the end user config. |
No, there's not a second method. Just create the file. |
I found another workaround. In my {
...
"scripts": {
"test": "NODE_ENV= jest",
...
},
...
} This prevents |
I know this is not the best practice but I've wrapped the warning logs in config.js with an if to get rid of the warning messages;
|
This avoid warning on build during testing see node-config/node-config#386 Signed-off-by: freddidierRTE <frederic-f.didier@rte-france.com>
This avoid warning on build during testing see node-config/node-config#386 Signed-off-by: freddidierRTE <frederic-f.didier@rte-france.com>
i have mocha tests being run in a spawned process with
NODE_ENV=test
and i'm getting these warnings in the output:i checked out #309 and read the source... it doesn't seem like there is any way turn them off?
The text was updated successfully, but these errors were encountered: