Skip to content
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

console.debug eats logging output in node 8 #134

Closed
divarvel opened this issue Jun 1, 2017 · 5 comments · Fixed by #177
Closed

console.debug eats logging output in node 8 #134

divarvel opened this issue Jun 1, 2017 · 5 comments · Fixed by #177
Assignees
Labels

Comments

@divarvel
Copy link
Contributor

divarvel commented Jun 1, 2017

Before node 8, console.debug did not exist, so the logger defaulted to console.log.
In node 8, console.debug exists, but does not log its arguments (I guess it can be done with an env variable or something).

It's not documented yet (https://t.co/JHrEGE3kT3), so I don't know how to tell it to display logs when CLEVER_VERBOSE is set.

@divarvel divarvel added the bug label Jun 1, 2017
@BlackYoup
Copy link
Member

It seems like this method is not yet implemented by Node. See nodejs/node#12675

@hsablonniere
Copy link
Member

@BlackYoup
Copy link
Member

From the documentation, console.debug() seems to be an alias to console.log() in node 9, I'm not sure it's relevant to use it.

@divarvel
Copy link
Contributor Author

divarvel commented Jan 8, 2018

I think we should not rely on inspecting the console object and use only console.log and console.error.

@hsablonniere hsablonniere self-assigned this Jan 9, 2018
@hsablonniere
Copy link
Member

I'm on it, I'll also refactor stuffs a bit ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants