Bug: Instantiating logger breaks console.error()

Describe the bug We are using tslog inside Blitz.js. It’s really great, but noticed that it’s causing a regression because it breaks the default behavior of console.error.

Before instantiating a tslog logger, console.error(new Error("Hello")) prints the following:

Error: Hello
    at Test (webpack-internal:///./pages/ssr.tsx:92:17)
    ...redacted

But after instantiating a logger, console.error(new Error("Hello")) prints this:

[Error: Hello]

As you can see, this is very bad because you can’t tell where the error is from.

In this case, third-party code is using console.error, so it’s not something we can change.

To Reproduce Steps to reproduce the behavior:

1. Run console.error(new Error("Hello"))
2. See error with stack trace
3. Instantiate logger: new Logger()
4. Run console.error(new Error("Hello"))
5. See there is no stack trace.

Node.js Version Node v12

OS incl. Version

  System:
    OS: macOS 10.15.7
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 5.43 GB / 64.00 GB
    Shell: 3.1.2 - /usr/local/bin/fish

[flybayer]

Sweet, thanks! Will test this in Blitz.

[terehov]

Thank you very much, that was really helpful! I have found and fixed the issue. Just need to update the tests to remain at 100% coverage. Expect an update today or at the latest tomorrow.