-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
winston:create-logger diagnostic cannot be turned off #1715
Comments
I believe this is caused by 3rd-Eden/diagnostics#20 |
This is caused by line no 54 in 'create-logger.js' where the developer has kept a debug line open for us.
I did comment this line manually and the problem is solved. |
Same question |
We are also having an issue with that line. Commenting it out is not an option, realistically. |
I can confirm that setting: |
None of the following .env lines removes this debug output in [email protected] nor [email protected]. Setting env on the command line does not work either.
Perhaps the act of initializing Winston in our code, or the Winston code itself, somehow negates the environment variables? |
Are you using the @dabh/diagnostics package in any other part of your repo? Are you using winston from somewhere where process.env isn't available? https://github.com/DABH/diagnostics?tab=readme-ov-file#adapters Haven't seen others report this issue so thinking it must be something special about your env or setup... |
Please tell us about your environment:
winston
version?winston@2
winston@3
node -v
outputs: v10.16.3What is the problem?
In the console I see a lot of messages coming from the
diagnostic
logger.What do you expect to happen instead?
I expected none of these internal winston debug messages in my console. I tried using
DEBUG=-winston:create-logger
andDIAGNOSTIC=-winston:create-logger
but neither worked.Other information
I saw another user report the same issue https://gitter.im/winstonjs/winston/archives/2017/11/22
And another user report the same issue https://stackoverflow.com/questions/55573448/disable-winstons-verbose-startup-logs
The text was updated successfully, but these errors were encountered: