update example to Pino v7 + transports

[quintesse]

It would be nice if the example could be updated to the latest version of Pino and would show the usage of transports. Especially because the issue I'm seeing is that transport modules get removed at build time because webpack thinks they are not being used.

[Enalmada]

@quintesse have you found a way to stop transport modules getting removed at build time?

I have not been able to work around this and trying to figure out what other people are doing to get pino working in next.js

 error Error [TypeError]: pino__WEBPACK_IMPORTED_MODULE_1___default(...).transport is not a function
    at <unknown> (webpack-internal:///(middleware)/./src/lib/logging/log-util.ts:25)
    at getLogger (webpack-internal:///(middleware)/./src/lib/logging/log-util.ts:25:72)
    at eval (webpack-internal:///(middleware)/./src/middleware.ts:26:80)

After some research, I suspect it has something to do with this
pinojs/pino-pretty#411
and this might solve it
https://github.com/pinojs/pino-webpack-plugin

[quintesse]

Hi @Enalmada . What I did was add unneeded imports for the transports. Like this:

import pino, { Logger, ... } from 'pino';

// Force Nextjs to keep these modules around!
import 'pino-pretty';
import 'pino-mongodb';
import '@logtail/pino';

.
.

transport = pino.transport({
    targets: [{
      target: "pino-pretty"
    }, ...
});