Suggestion: Use stderr for diagnostic output instead of stdout

[danidb]

DaisyUI is awesome, good times. Thank you. A "DX"-ish suggestion:

I've had issues in toolchains with prettier-plugin-tailwindcss and similar steps that involve stdout/stdin and trigger (somehow) the logging in daisyUI, locally and in CI. My issues are similar to those linked below. DaisyUI's logging was problematic for me because tools will expect stdout to only contain program output...but I didn't want to turn off the logs.

tailwindlabs/tailwindcss#8380
#1413

To keep logs available in the terminal but avoid issues with tools that work on stdin/stdout, it's common/conventional to send diagnostic or debug logs to stderr instead. Node sends console.log to stdout and console.error/console.warn to stderr so I usually just patch this behavior by swapping out the problematic console.log in daisyUI for a console.error/warn on my end with patch-package and that takes care of it.

Can gladly contribute/PR. Cheers.

[saadeghi]

This is neither a warning nor an error.
stderr must be used for errors.
I can't confirm that using stderr is not going to break some other build pipeline that treats stderr as an error and exits the process because of it.
I think this is something prettier-plugin-tailwindcss must fix.