pino-pretty add "name" property to process number instead of log it

[leozhao0709]

const logger = pino({
  level: config.LOGGER.LEVEL,
  transport:
    process.env.NODE_ENV !== 'production'
      ? {
          target: 'pino-pretty',
        }
      : undefined,
});

logger.info({ name: '123', orderBy: [] });

with pino-pretty, it logs like this:

in production with json format, I can see the name property in logs. So I think this is just a pino-pretty issue.

[jsumners]

Would you like to send a Pull Request to address this issue? Remember to add unit tests.

[leozhao0709]

@jsumners I was looking the source code and seeing this part

https://github.com/pinojs/pino-pretty/blob/master/lib/constants.js#L45-L54

Seems these are pre-defined keys that used by Pino? In my local, I only see 'pid', 'hostname', 'level' and 'time' was used by pino. But if other keys like 'name', 'timestamp' and 'caller' are some predefined keys that may used by pino or ecosystem, then probably we can't fix it.

Can you confirm these keys? If these are used by Pino on purpose, we may need document it somewhere.

[jsumners]

I have not been able to follow the description of the problem you are encountering. I cannot answer.

[qmzmdqs]

bunyan

name This is too common. Maybe change the field.