Pino 8.17.0 breaks logging from catch in TypeScript

Question

Pino 8.17.0 breaks logging from catch in TypeScript

otowncaleb opened this issue 5 months ago · 3 comments

#1783 seems to have re-introduced #1115 as LogFn no longer accepts an object of type unknown, which is what TypeScript emits for caught errors.

Answer 1 · 2023-12-14T01:01:10.000Z

Ah - I see now from the discussion in that PR that this is intentional. This is unfortunate as it constitutes a breaking change for those who previously logged this way.

From a DX perspective it's also somewhat surprising that Pino won't accept the error object as-is.

Answer 2 · 2023-12-14T09:21:58.000Z

Thanks, will revert asap.

#1866

Answer 3 · 2024-01-14T00:04:55.000Z

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.