-
Notifications
You must be signed in to change notification settings - Fork 5
Doesn't respect concatOutput #10
Comments
We don't support An example of usage: var concat = require('gulp-concat');
var gulp = require('gulp');
var gulpif = require('gulp-if');
var soynode = require('gulp-soynode');
gulp.task('soy', function() {
return gulp.src(soySrc)
.pipe(soynode())
.pipe(gulpif('*.soy.js', concat('bundle.js')))
.pipe(gulp.dest(soyDest));
}); Let me know if this worked for you. |
Works like a charm! Thank you very much - once again. I made use of gulp-ignore to exclude the soy files - as they where not desired in the final output.
|
Glad to know it worked! I'll keep this open because it's still weird that we don't respect an option that soynode accepts. We can either start using it as well or warn explaining that concatenating should be done via gulp-concat. |
Making use of soynode options would be nice - though, I'll take whatever works. :) If you end up going with a warning then adding your example to the README or wiki would probably go a long way to answer this. I was surprised that the original .soy files where forwarded to the output - but then again, I'm rather new to npm,gulp so maybe that contribute to my confusion. Though that snippet above works great - single compiled JS file. :) |
I tried to use
concatOutput
andconcatFileName
to create a single concatenated output file. The temp folder will produce the file, butgulp-soynode
will copy the individually compiled files.I also tried to use
gulp-concat
on the stream but the just concatenated the source.soy
files.Is this not supported - or am I using it wrong?
The text was updated successfully, but these errors were encountered: