Support for pino transports?

[yorch]

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

[styfle]

There's a similar issue #794 that suggested --asset-builds flag

[yorch]

@styfle did it work for you? I tried it before creating the issue but couldn't make it work

[ghost]

--asset-builds didnt work for me either with pino, so i just it as externals while playing around.

It also doesn't show up in the help text at all as per the readme. I went back through the last few releases and it has never showed up in in the help text even I think in the one in which it was introduced, so it's probably more of a UI oversight in that case.