Can't use custom levels in multistream with TypeScript

[frzsombor]

The following code worked totally fine in JS, but I'm currently in the process of converting my NodeJS app to typescript.
I would like to use custom levels in multistream with TypeScript, but the definitions are not allowing me to do so.
I have this file, where I prepare and configure pino to use it in different parts of my application:

import * as fs from 'fs';
import pino, { StreamEntry } from 'pino';
import pretty from 'pino-pretty';

const customLevels = {
    debug   : 1,
    info    : 2,
    network : 3, // <- my custom level
    error   : 4,
};

const pinoOpts = {
    //...
    useOnlyCustomLevels: true,
    customLevels: customLevels,
    //...
};

const multistreamOpts = {
    dedupe: true, //send logs only to the stream with the higher level
    levels: customLevels,
};

const streams: StreamEntry[] = [
    { level : 'debug',   stream : fs.createWriteStream(`./log/log-debug.log`,   { flags: 'a' }) },
    { level : 'info',    stream : pretty() },
    { level : 'info',    stream : fs.createWriteStream(`./log/log-info.log`,    { flags: 'a' }) },
    { level : 'network', stream : fs.createWriteStream(`./log/log-network.log`, { flags: 'a' }) },
/*             ^^^^^^^
                  └ - ❗ TypeScript error ❗
*/
    { level : 'error',   stream : pretty() },
    { level : 'error',   stream : fs.createWriteStream(`./log/log-error.log`,   { flags: 'a' }) },
];

export default pino(pinoOpts, pino.multistream(streams, multistreamOpts));

However, I get the following error where I define streams:
Type '"network"' is not assignable to type 'Level | undefined'.ts(2322)

The reason is that in pino.d.ts, Level is explicitly defined to be "fatal" | "error" | "warn" | "info" | "debug" | "trace" and no matter how many times and different approaches I tried to override/extend the definition, none of my attempts worked.

[mcollina]

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

[frzsombor]

@mcollina I'm quite new to TS, and not sure what would be the best practice, to fix this issue.
However if you, or someone could help me with an idea, I can try to implement it in a PR.

[aalzubidy]

I can submit a PR, is it removing the type checking for that one so users can add custom levels or map the custom levels values to the type?

[frzsombor]

@mcollina @VladimirMikulic Please correct me, if I'm wrong, but I think this issue still exists, I can still only get around this problem by using @ts-ignore on the line above the custom level, even with the latest v8.10.0 version.

[ramiel]

I see the very same error

[mcollina]

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

[mcollina]

cc @kibertoad

[Puppo]

@mcollina, Could I help with this bug? I have an idea in mind.

[simoneb]

This was actually closed by #1778. @mcollina can you close this issue?

[mcollina]

thx @simoneb

[github-actions]

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