Skip to content
This repository has been archived by the owner on Jul 31, 2018. It is now read-only.

Browserify #59

Open
rstacruz opened this issue Feb 10, 2016 · 6 comments
Open

Browserify #59

rstacruz opened this issue Feb 10, 2016 · 6 comments

Comments

@rstacruz
Copy link

I know this repo represents your personal preferences, but I'm curious on why the choice of webpack over browserify.

  • browserify can do hot module replacement via browserify-hmr and it's pretty easy. no need for an external dev server like webpack-dev-server.
  • postcss is supported via browserify-postcss, but why bother adding your css into your js files when they can be compiled as .css files?
  • vendor.bundle.js can be done via factor-bundle
  • babel is supported via babelify

using browserify would probably reduce 60 lines of webpack.config.js into just ~10 lines inside package.json, and is much simpler to boot.

@tj
Copy link
Owner

tj commented Feb 10, 2016

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.

@rstacruz
Copy link
Author

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
#59 (comment)
.

@tj
Copy link
Owner

tj commented Feb 10, 2016

Yeah maybe, seems snappier now than it was when I tried last, at least for the tiny demo app in there

@tj
Copy link
Owner

tj commented Feb 10, 2016

Is it possible to use postcss without streams? Can't stand node streams, I just want non-js config ideally

@rstacruz
Copy link
Author

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
#59 (comment)
.

@tj
Copy link
Owner

tj commented Feb 10, 2016

cool I'll try it out later on my stuff and see how it goes

@tj tj changed the title Question: why webpack? Browserify Feb 10, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants