Using console log in global scope crashes the execution about alfy HOT 3 OPEN

I also don't understand how do you "console debug" anything using alfy without effectively breaking the workflow execution.
ATM it's either you get the debug logs or you get proper workflow execution, never both.

Any of the alfy/console logs will break the execution of the workflow:

import alfy from 'alfy'

alfy.log("my alfy.log()")
alfy.error("my alfy.error()")
console.info("my console.info()")
console.debug("my console.debug()")
console.error("my console.error()")

alfy.output(
    [
        {
            title: "My title"
        }
    ]
)

You will see the various log messages and My title being displayed in debug console, but the workflow execution will be broken, it crashes as alfred cannot parse the output.
Using any of the above logs crashes the exectuion of the workflow.

The big question here is how do you add debug log but at the same time don't crash the workflow execution?

from alfy.

alfy.log simply passes it to console.error. Alfred documents that you can output to stderr for debugging.

https://www.alfredforum.com/topic/9170-alfred-3-tip-use-stderr-to-output-to-the-debug-console/

from alfy.

I'm also confused as to how this is supposed to work. I understand that alfy.log() is simply a wrapper around console.error(); however, when I try to use it, I end up seeing two items arrays getting printed to the console, which doesn't seem right.

FYI... If I comment out the following line in Alfy, everything works as expected:

// hookStderr(alfy.error);

Alfy seems to be trying to do two conflicting things with regards to stderr:

#86 (comment)

from alfy.