TestCafe launched via CLI does not print reporter's stderr in the console since 1.15.0

[VasilyStrelyaev]

What is your Scenario?

Try the following reporter stab to reproduce the issue:

module.exports = function () {
    console.log('Hello world!');
    console.error('Oh, you don\'t say!');

    return {
        noColors: true,
        
        reportTaskStart (/* startTime, userAgents, testCount */) {
        },

        reportFixtureStart (/* name, path */) {
        },

        reportTestStart (/* name, testMeta */) {
        },

        reportTestDone (/* name, testRunInfo */) {
        },

        reportTaskDone (/* endTime, passed, warnings */) {
        }
    };
};

What is the Current behavior?

Hello world!

What is the Expected behavior?

Hello world!
Oh, you don't say!

What is your public website URL? (or attach your complete example)

What is your TestCafe test code?

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

1. Generate an empty reporter (testcafe-reporter-foobar) with the Yeoman generator
2. Add the abovementioned console.log and console.error lines:

   console.log('Hello world!');
   console.error('Oh, you don\'t say!');

3. npm link the module
4. Use the reporter when running any test:

   testcafe chrome test.js --reporter foobar

(you may also have to check the reporter's main setting in package.json because it's not generated correctly by generator-testcafe-reporter).

TestCafe version

1.15.0 +

Node.js version

No response

Command-line arguments

Browser name(s) and version(s)

No response

Platform(s) and version(s)

No response

Other

No response

[VasilyStrelyaev]

Indeed, your commit fixes the example with an empty reporter... Thank you!
But it sadly does not seem to fix the dashboard reporter.

New steps to reproduce:

1. npm install testcafe-reporter-dashboard
2. export TESTCAFE_DASHBOARD_AUTHENTICATION_TOKEN= (yes, empty, to generate an error)
3. testcafe chrome test.js --reporter dashboard

No errors printed.

If you now modify the reporter's node_modules/testcafe-reporter-dashboard/lib/logger.js - change console.error and console.warn to console.log - errors will be displayed.

[VasilyStrelyaev]

Can confirm that with 1.18.4-rc.3 the reporter prints the errors as expected.