Perhaps maybe a Webpack wrapper? A large configuration object can seem cryptic until you really learn how all the properties affect the build process.
For example:
webpack
.entry({
'app': './app/index.js',
'vendor: './app/vendor.js'
})
.load('typescript', /\.ts$/)
.load('sass', /\.scss$/)
.plugins([new webpack.optimize.plugin])
.output('./dist');
Or:
module.exports = webpack.entry(...).load(...).output(...)
@jaesung2061 We would love some input and feedback on better documentation. I'm not sure if we _need_ more ways to "skin the cat", however but giving your perspective and incorporating it into documentation could be very beneficial.
Also looks like this may already exist:
Not that you guys need it. Just curious. Also, webpack-stream
is just a Gulp plugin. What I was asking was if you guys thought about an API similar to Gulp.
Most helpful comment
Not that you guys need it. Just curious. Also,
webpack-stream
is just a Gulp plugin. What I was asking was if you guys thought about an API similar to Gulp.