Andrew Brindamour

@xunziheng is correct. This is a bug. The cause of this is that the NestJS `Logger` class is delegating the `error()` message to `WinstonLogger`, and in the case that a...

I should note that this is all caused by the fact that `Logger.error(message: any, stack?: string, context?: string)` is ambiguous at invocation time due the presence of multiple optional parameters...

Opened a PR with a fix: https://github.com/gremo/nest-winston/pull/513 Since things were already ambiguous, the fix has its downsides. Feel free to accept or reject.

@faithfulojebiyi I have absolutely read the documentation if it wasn't already clear. The issue isn't the documentation, it is that when you implement a logger that works with Nest, you...

I agree this is a bit confusing and me and my fellow engineers have been tripping over this too. For what it's worth, here's what we do: First, register WinstonLogger...

I'm also seeing the primary symptom here ("When setting up multiple watches with independent patterns, any event on one file will fire in both."). However, I'm not seeing incorrect events,...

I just spent a good couple of hours debugging this problem, and here's what I've found. The biggest issue is that React doesn't respect the `displayName` property any more, which...

If you look at the latest version React's `ReactMemo.js` which you cited in #3192 , you'll see that they sneakily added another check: the component must also not have a...

Some things that might be tricky... I haven't used Bob's mod but I've read a bit about it and I know its very comprehensive. Does it add any of the...

There's now a bulk import/export function in the tool. It's not a url, but its sharable. Does this fulfill the request or would you like to see the URL still?