Describe the bug Error in 6.1.0 when an Experimenta

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

Sure <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url

6.1.0 - Errors when ExperimentalWarning is caught about log-process-errors HOT 3 CLOSED

ehmicky commented on May 21, 2024

6.1.0 - Errors when ExperimentalWarning is caught

from log-process-errors.

Comments (3)

ehmicky commented on May 21, 2024

Hi @abrenneke,

Thanks for reporting this bug!

This should be fixed in 6.1.1.

By curiosity, could you please copy/paste the output of the following command?

npx envinfo --system --binaries --browsers --npmPackages log-process-errors

And also describe how you called log-process-errors, including any potential options.

from log-process-errors.

abrenneke commented on May 21, 2024

Sure @ehmicky thanks for fixing this so quickly!

npx: installed 1 in 1.242s

  System:
    OS: Linux 4.13 CentOS Linux 7 (Core)
    CPU: (6) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
    Memory: 480.59 MB / 7.79 GB
    Container: Yes
    Shell: 5.0.2 - /bin/zsh
  Binaries:
    Node: 13.9.0 - ~/.nvm/versions/node/v13.9.0/bin/node
    Yarn: 1.22.4 - ~/.yarn/bin/yarn
    npm: 6.13.7 - ~/.nvm/versions/node/v13.9.0/bin/npm
  Browsers:
    Chrome: 75.0.3770.80
  npmPackages:
    log-process-errors: 6.1.0 => 6.1.0

My log-process-errors call is like this:

const ignoreWarnings = [
    // Ignore warnings about experimental features
    /queueMicrotask\(\) is experimental/,
    /Conditional exports is an experimental feature/
];

logProcessErrors({
    level: {
        warning: error => ( ignoreWarnings.some( r => r.test( error?.message ) ) ? 'silent' : 'default' ),

        // Disabled for now
        multipleResolves: constant( 'silent' )
    }
});