You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Debug shows different timestamp formats across package and project #867
Mrh yeah sorry about that. I'm still trying to figure out the best way to fix this problem. Unfortunately it's not straightforward or obvious to solve. #556 was (is) supposed to address this issue, but with the advent of module loaders and losing access to the import cache, things have gotten more complicated.
Activity
imjamesb commentedon Feb 4, 2022
I also attempted to use the override feature, did not work though.
Qix- commentedon Feb 4, 2022
Mrh yeah sorry about that. I'm still trying to figure out the best way to fix this problem. Unfortunately it's not straightforward or obvious to solve. #556 was (is) supposed to address this issue, but with the advent of module loaders and losing access to the import cache, things have gotten more complicated.
imjamesb commentedon Feb 4, 2022
Ah I see, so if I understand correctly, this is Express' doing?
imjamesb commentedon Feb 4, 2022
For some reason, when degrading to 2.6.9 (the same version express depends on) my logs use the GMT format, and express' logs uses the ISO format.
Weird..
Qix- commentedon Feb 4, 2022
What does
npm ls debugshow?imjamesb commentedon Feb 4, 2022
Qix- commentedon Feb 4, 2022
Not sure that
^is allowed in overrides. Maybe start with just{ "overrides": { "debug@2.6.9": { "debug": "4.3.3" } } }Does that work?
imjamesb commentedon Feb 4, 2022
Qix- commentedon Feb 4, 2022
No idea then :/ Which order are you importing
debug? Do you first import it before or afterexpress? If after, try importing it before anything else.Qix- commentedon Feb 4, 2022
Actually looking at your
npm lsoutput it doesn't appear the override is working. Are you using package-lock.json files per chance?Try deleting it (I have them turned off by default, typically - they add no value) then re-installing.
imjamesb commentedon Feb 4, 2022
Yes, I'll delete the lockfile and try again ;)
imjamesb commentedon Feb 4, 2022
Okay, so for some reason my own debugs no longer work - but express' do
Qix- commentedon Feb 4, 2022
By "not work" do you mean just no output? Or is there an error?
Try blowing away both
node_modulesand any lockfiles and re-installing from scratch, then.imjamesb commentedon Feb 4, 2022
Got them back
It didn't output, even though DEBUG was set to
*, it was because dotenv was loaded after debug I thinkimjamesb commentedon Feb 4, 2022
The override still doesn't work
imjamesb commentedon Feb 4, 2022
Turns out this was the way to go, it works using this. Probably time to do a couple of version bump PRs
Qix- commentedon Feb 4, 2022
Oh right, that makes sense 🙃 sorry I didn't catch it the first time haha.
Yeah seems right! Feel free to ping me on any you may open.
Going to go ahead and close this now. Let me know if there's anything else.
imjamesb commentedon Feb 4, 2022
Awesome, thanks for your help, awesome library!