Pino is a logger that has the concept of transports, that are started in a worker thread, so the transports (which can be other packages) are not directly import by the code, but just referenced by name. For instance:
const pino = require('pino')
const transport = pino.transport({
target: 'pino-pretty',
options: { destination: 1 } // use 2 for stderr
})
pino(transport)
Being pino-pretty another NPM package.
More info: https://github.com/pinojs/pino/blob/master/docs/transports.md#transports
After compiling a project and trying to run the compiled version, Pino cannot obviously find the used transports (ie: pino-pretty).
Any idea on how to support this or work around it?
Thanks
Pino is a logger that has the concept of transports, that are started in a worker thread, so the transports (which can be other packages) are not directly import by the code, but just referenced by name. For instance:
Being
pino-prettyanother NPM package.More info: https://github.com/pinojs/pino/blob/master/docs/transports.md#transports
After compiling a project and trying to run the compiled version, Pino cannot obviously find the used transports (ie:
pino-pretty).Any idea on how to support this or work around it?
Thanks