-
-
Notifications
You must be signed in to change notification settings - Fork 17.2k
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
DEBUG=express:* does not work in [email protected] #6280
Comments
But notably An aside, splitting like this makes it more difficult to debug router under the |
+1 AFAIK this was not an intended move. I will consider this as a bug and one of the reason to not tag express@5 as |
This doesn't seem to be a bug, it was done in this commit(pillarjs/router@0b5a0a6) and is listed in the changelog for releasing version 2 of the router (pillarjs/router#60). Although +1 on bringing it back, it's useful for debugging while we have a new logger. |
Directly using DEBUG=express:* node index.js because express no longer directly using the debug package
|
I swear I had written a reply to this, sorry I must have accidentally forgotten to hit send, sorry. Maybe was it on the router repo or slack or something? Either way, I from what @bjohansebas showed it was done on purpose, I just wish we knew more than what the In the long run I would very much like to remove this dependency and use a proper logger ( So, for today since the change landed nearly 4 years ago and folks are just now noticing, lets not make a hasty decision? We can for sure add this to the "fix before latest" release, but I think we should see if we could easily land a logger integration, since that would be long term better anyway. |
There was a discussion about removing |
Description
Debugging Express said
"To see all the internal logs used in Express, set the DEBUG environment variable to express:* when launching your app."
DEBUG=express:* node index.js
But it does not work in [email protected]
There is also no answer on Moving to Express 5
Expectations
How to debug in [email protected]?
The text was updated successfully, but these errors were encountered: