potential for black-holing log messages via transitive dependency on gulplog

gulp-util.log checks for hasGulplog on module initialization and if present, defers logging to gulplog.info, which in turn will eat any messages below error (I believe) unless there is explicitly an event handler for the other levels (info, warn, etc.).

This can happen ‘accidentally’ if a transitive dependency uses gulplog.

It seems like the reasonable thing to do is to use gulplog.error to ensure all logging is output properly.

[ischneider]

However, I think you might actually be saying that some dependency is using gulplog, which makes it available in the global scope but you aren’t using the new gulp-cli, so no logs are being logged. Is that correct?

Correct and I can verify that using the gulp executable from gulp-cli produces the desired behavior, i.e. gulp-util.log produces output even when gulplog is present.

This is fine longer term, but it seems like a potential problem for the unaware - case in point: me and my time lost 😦

Super simple example

require('gulplog');
require('gulp-util').log('foobar');

When run using global gulp, no ‘foobar’. When using locally installed gulp from gulp-cli, ‘foobar’ is logged.

Thanks 😄

[phated]

This problem won’t be solved until we get the community transferred off gulp installed globally and installing gulp-cli instead ☹️