Open rstacruz opened 8 years ago
I'm cool with it if the hmr stuff is as fast, I've had issues with browserify being slow in the past but that was pre-hmr. I don't really care what builder it is as long as it supports the stuff I want to use, at a glance it seemed to have less adoption these days.
Ahh.. Sounds like watchify will fix that for you :)
On Thursday, February 11, 2016, TJ Holowaychuk notifications@github.com wrote:
I'm cool with it if the hmr stuff is as fast, I've had issues with browserify being slow in the past but that was pre-hmr
— Reply to this email directly or view it on GitHub https://github.com/tj/frontend-boilerplate/issues/59#issuecomment-182470341 .
Yeah maybe, seems snappier now than it was when I tried last, at least for the tiny demo app in there
Is it possible to use postcss without streams? Can't stand node streams, I just want non-js config ideally
You mean from the cli?
browserify -t [ browserify-postcss --plugin cssnext ] -t browserify-css
Or expressing its equivalent in the package.json "browserify" field. Disclaimer: haven't actually tried it, so it probably doesn't work as is. Haha
On Thursday, February 11, 2016, TJ Holowaychuk notifications@github.com wrote:
Is it possible to use postcss without streams? Can't stand node streams, I just want non-js config ideally
— Reply to this email directly or view it on GitHub https://github.com/tj/frontend-boilerplate/issues/59#issuecomment-182485497 .
cool I'll try it out later on my stuff and see how it goes
I know this repo represents your personal preferences, but I'm curious on why the choice of webpack over browserify.
using browserify would probably reduce 60 lines of webpack.config.js into just ~10 lines inside package.json, and is much simpler to boot.