Formatting errors with gulp-util about gulp-coffee

[yocontra]

How does .on('error', console.error)) look?

[rhys-vdw]

Same output with console.error.

Okay, so this prints correctly:

I told a lie, they were all broken. At some stage while I was playing with different permutations I though I had it working with the following code, but no longer. I'm not even sure this is a gulp-coffee problem now, as it's working fine in my backend project.

gulp.task('scripts', function (done) {
  return gulp.src(appSrc.scripts)
    .pipe(coffee())
    .on('error', util.log)
    .pipe(gulp.dest(compileDest.scripts))
    .pipe(size())
    ;
});

And both of these print output as above:

gulp.task('scripts', function (done) {
  return gulp.src(appSrc.scripts)
    .pipe(coffee())
    .on('error', util.log)
    .pipe(gulp.dest(compileDest.scripts))
    .pipe(size())
    ;
});

gulp.task('scripts', function (done) {
  return gulp.src(appSrc.scripts)
    .pipe(coffee().on('error', util.log))
    .pipe(gulp.dest(compileDest.scripts))
    .pipe(size())
    ;
});

[yocontra]

Different versions of gulp-util? Are you sure everything is up to date with the latest?

[edmundito]

I peeked into gulp-util (3.0.6) myself and found that for whatever reason, the error is not being formatted toString(). This is is how I worked around it in my gulpfile:

$ = require('gulp-load-plugins')()
errorHandler = (error) -> $.util.log error.toString()

# Inside the task...
.pipe($.coffee(bare: true).on('error', errorHandler))

[yocontra]

@edmundito Something that needs to be fixed in gulp-util? What were your findings?

[edmundito]

Yes, this is mainly related to the implementation of the log() function in gulp-util 3.0.6. I've noticed that master is currently a bit different, however what I found is that it has to do with the behavior of console.log in Node (as well as Chrome and Safari). console.log seems to not respect the toString declaration when outputting objects by themselves:

$ node
> function Cls() {}; Cls.prototype.toString = function () { return 'the string'; }
[Function]
> var c = new Cls()
undefined
> console.log(c)
Cls {}
undefined
> console.log(c.toString())
the string
undefined
> console.log('' + c)
the string
undefined
> console.log.apply(console, [c, c, c])
Cls {} Cls {} Cls {}

This could also be the cause behind the result in gulpjs/gulp-util#74.

[yocontra]

The PluginError class is a disaster in gulp-util right now - there are plans to replace it with something simpler called BetterError but I haven't had time to dedicate to it.

With that - I'd take a PR to fix this issue in gulp-util if any of you have time.

[yocontra]

Closing, this was split out of gulp-util into the plugin-error module and we use that now. Any fixes for formatting should go there.