Pino Transport not supported in Cloudflare Workers

[rohinlohe]

@calcsam, can you provide more context re: pino transport not being supported in Cloudflare Workers.

[jasnell]

/cc @mcollina

[jasnell]

The Node.js specific version of pino does not work in workers for sure due to a number of the dependencies and internal requirements. However, it ought to be possible with a few tweaks here and there to get the browser version of pino working (which is really just a browserified version of the module ... https://getpino.io/#/docs/browser). For the most part this variation just sits on top of console.log(...) for generating output as far as I understand (@mcollina could say for certain). What I don't know is what set of browserified Node.js APIs the browser version of Pino still requires. It's also not clear if the browserified version of pino requires mechanisms like eval() or new Function() that we explicitly disable. Either way, it would be great to have a version of pino that works out of the box with workers. Really we would just need to assign someone to build it.

[mcollina]

pino transports make no sense in workerd because in workerd executions are short lived, while transports make sense for long running processes. If you want to craft a pino equivalent to run in workerd, you’d need to spawn a new worker for each transport.

Having said that, the browser implementation of pino should work on workerd.