I've got a setup where I'm trying to compile multiple entry points, each with their own config, which has lead me to "multi-compile" mode. In the webpack-stream test, I can see how different output.filenames are supported, but I can't figure out if output.path is supported. Similar issue here, but not related to mult-config:
https://github.com/shama/webpack-stream/issues/133
So, is .pipe(gulp.dest('dist/')); required for webpack-stream to work? In my current gulp task, I'm simply creating/returning the stream created by webpack-stream, without actually using a gulp.src('src/entry.js'), which seems to work ok (I'm seeing webpack getting built in my logs), but I'm not seeing files actually getting written by Webpack to disk.
I've got a setup where I'm trying to compile multiple entry points, each with their own config, which has lead me to "multi-compile" mode. In the webpack-stream test, I can see how different output.filenames are supported, but I can't figure out if output.path is supported. Similar issue here, but not related to mult-config: https://github.com/shama/webpack-stream/issues/133
So, is
.pipe(gulp.dest('dist/'));
required forwebpack-stream
to work? In my current gulp task, I'm simply creating/returning the stream created by webpack-stream, without actually using agulp.src('src/entry.js')
, which seems to work ok (I'm seeing webpack getting built in my logs), but I'm not seeing files actually getting written by Webpack to disk.Thanks for your help!