CLI progress when processing multiple URLs

[pocketjoso]

CLI progress when processing multiple URLs

[pocketjoso]

To be fair here, I must ask:

Am I right in thinking this should be done by the Node module? Or should it be left to the end user to log something in the callback function?

[fatso83]

The node module should not output anything. That does not stop us from doing it in the stand alone version! Once we remove the old behaviour of outputting the result to stdout, and rather output all css to file, stdout will be strictly for user viewable output in the standalone process. We simply refrain from using it in the Node module. The node module uses anything output on stderr, so don't use that for debug output.

[fatso83]

So in essence, you can sprinkle as many console.log statements you feel like in core.js, as it won't affect the standalone at all (after we remove the old behaviour, at least)

[fatso83]

Any reason this is open still? Seems resolved to me (as a kind of #wont-fix)

[pocketjoso]

I still want some progress when the command is run; if you're saying it's a no go for a Node module, then at least for the standalone version.

So would the idea be then to conditionally add log statements when in standalone mode?

[fatso83]

Closing? Ref #41

[pocketjoso]

Yep.