We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After I started using @slack/client in a project, my logs are being printed differently. Running some tests, this shows:
console.info node_modules/@slack/client/dist/logger.js:26 [INFO] undefined {"message":"received cancel message from redis","hash":"some-random-hash"}
As it turns out, @slack/client/dist/logger.js seems to be monkey patching functions defined/used by loglevel.
Is there any way to reset this at the start of my project's runtime or prevent it altogether from being patched?
I know this might by slack specific, but there's a chance something can be done in loglevel's side.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
After I started using @slack/client in a project, my logs are being printed differently.
Running some tests, this shows:
console.info node_modules/@slack/client/dist/logger.js:26 [INFO] undefined {"message":"received cancel message from redis","hash":"some-random-hash"}
As it turns out, @slack/client/dist/logger.js seems to be monkey patching functions defined/used by loglevel.
Is there any way to reset this at the start of my project's runtime or prevent it altogether from being patched?
I know this might by slack specific, but there's a chance something can be done in loglevel's side.
The text was updated successfully, but these errors were encountered: