Updates to pino v7, as pino.multistream is already in pino.

[mcollina]

I also updated tap.

[glensc]

pino.multistream is already in pino

what does this mean? this package is no longer needed to handle multiple streams?

I how to do the example In readme without pino-multi-stream package?

var fs = require('fs')
var pinoms = require('pino-multi-stream')
var streams = [
  {stream: fs.createWriteStream('/tmp/info.stream.out')},
  {level: 'fatal', stream: fs.createWriteStream('/tmp/fatal.stream.out')}
]
var log = pinoms({streams: streams})

[mcollina]

That's the only thing that is left in this module. We can create a multistream with https://getpino.io/#/docs/help?id=multi-stream.

[glensc]

Sorry, what is the "that's" that's left in this module? what is what can't be done with pino 7?

[mcollina]

This is the equivalent of the previous example using "just" pino:

var fs = require('fs')
var pino = require('pino')
var streams = [
  {level: 'debug', stream: fs.createWriteStream('/tmp/debug.stream.out')},
  {level: 'fatal', stream: fs.createWriteStream('/tmp/fatal.stream.out')}
]

var log = pino({
  level: 'debug' // this MUST be set at the lowest level of the
                 // destinations
}, pino.multistream(streams))

It's a nice wrapper on top of it, fixing the levels so that there is no needed for manually managing it.

[glensc]

And what is that different from something like this?

    const transport = pino.transport({
      targets: [
        {
          level: 'debug',
          target: "pino-pretty",
          options: {},
        },
        {
          level: "trace",
          target: "pino/file",
          options: { destination: "/path/to/store/logs" },
        }],
    })
    const logger = pino({
      transport,
    });

[mcollina]

Nothing in practice, it's more of a convenience method.