fix: stricter type

[climba03003]

Fixes #1293

Notable Changes:

• Remove Record<string, any> from Logger.
• Update tsconfig.json, I think the current include should be exclude because it should not compile the test file which may contain error.
• Reflect customLevels options and combine it with Logger.

I think it can provide even more stricter type on the options like useOnlyCustomLevels, level, etc. But it require a heavy refactor and times.

[climba03003]

The CI failure is actually not related to my changes.

[climba03003]

Not sure why it is inside the type check.
I cannot find the relevant code in js.

[mcollina]

Should we update the doc?

[mcollina]

lgtm

[climba03003]

Should we update the doc?

I don't know which file is appropriate for the update. Currently, pino do not provide a TypeScript specific document.

[mcollina]

Ah don't worry then. Let's just wait for @kibertoad.

[kibertoad]

This looks great!

[MaikuMori]

I believe that this broke something.

Basically, Logger<{customLevels}> is not carried over after logger.child() call and I get type error on the child instance when using a custom level function.

const logger = pino({
  customLevels: {
    warning: 400,
  },
  useOnlyCustomLevels: true,
});
const child = logger.child({whatever:true});
// Type error.
child.warning("Hello there");

This was not the case before.

EDIT:
TS version: 4.5.5

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.