Echo JS 0.11.0

`First problem of react is HTML inside our JS files and there is no way to make them separate.`

That is not a problem but one of the main features of react. So if there is no feature to separate the html from a component, maybe it is with intent ;)

My reason to switch to webpack were two things. First the hot plug for react, where you can live reload reactJs components in your app without loosing the app state. The second was the ability to compile an app in to multiple parts for lazy loading. After a discussion here on echojs, I realize that the later is possible in  browserify as well. 

Which points me to my main problem with browserify, the docs. There is the webpage, the github page + wiki and the browserify handbook. Everyone as long markdown files. So if I want to find out the code splitting feature exists, I have to read all of this to find it in the last part of the handbook. So maybe the homepage should provide more information what browserify offers, beside bundling modules to use in the browser.

Why would one need am alternative browser for IE6 in the 2002. Who needs another MVC framework after backbone was released. Even why browserify was invented after requireJS solved all our problems for client side loading. I don't think that `Why another …` is a good question.

Maybe cause slides like this leaves a lot of open questions. Most of the slides only mention the `what` but not the `why` and `how`. Sure all of this was mentioned in the talk but the slides without the talk are not that helpful.

Same here, returns 404

Split points are called partition-bundle: https://github.com/substack/browserify-handbook#partition-bundle

CSS bundles can be created with a specail transformer: https://github.com/davidguttman/cssify

Ok, maybe its just me knowing browserify not well enough, but maybe its that there are not enough articles that promote advanced features. Even the docs don't tell about this. The only bit I can find is in one of the last sentences of the handbook (and only cause you mentioned that this feature exists). So we are back to your initial point about the reading tons of docs ;)

Btw. for me the feature of having multiple entry points is essential for a package manager on client side.

Yes thats the CSS part, didn't know that there is a similar feature in browserify.

Split points means, that you can have can split your application into different parts that will be loaded when needed, instead of compiling the whole app into one file.

React hot load is indeed bundled to reactJS, its a cool feature where you can run your app, change a react module and only this module will replaced in your running in the browser while the state and all other modules sty the same.

Sure, but webpack solves a lot more problems then browserify, eg. bundle CSS per module, split points or the react hot loader. Also requireJs wasn't that hard to get into.

So how is this different to the use of npm and webpack/browserify?