Debug shows different timestamp formats across package and project

[imjamesb]

Debug shows different timestamp formats for body-parser, express and my project.

[imjamesb]

I also attempted to use the override feature, did not work though.

[Qix-]

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]

Ah I see, so if I understand correctly, this is Express' doing?

[imjamesb]

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-]

What does npm ls debug show?

[imjamesb]

[Qix-]

Not sure that ^ is allowed in overrides. Maybe start with just

{
    "overrides": {
        "debug@2.6.9": {
            "debug": "4.3.3"
        }
    }
}

Does that work?

[imjamesb]

[Qix-]

No idea then :/ Which order are you importing debug? Do you first import it before or after express? If after, try importing it before anything else.

[Qix-]

Actually looking at your npm ls output 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]

Yes, I'll delete the lockfile and try again ;)

[imjamesb]

Okay, so for some reason my own debugs no longer work - but express' do

[Qix-]

By "not work" do you mean just no output? Or is there an error?

Try blowing away both node_modules and any lockfiles and re-installing from scratch, then.

[imjamesb]

Got them back

It didn't output, even though DEBUG was set to *, it was because dotenv was loaded after debug I think

[imjamesb]

The override still doesn't work