JSX has the advantage of being fast, but the disadvantage that it needs to be preprocessed before working. By using template string virtual-html, we can have it work out of the box, and optimize it by writing a browserify transform. Best of both!
See also: https://github.com/choojs/nanohtml#static-optimizations
(this person later recommends this library)
require('modules') in the browser
Use a node-style require() to organize your browser code and load modules installed by npm.
Now just use the browserify command to build a bundle starting at main.js:
browserify is a tool for compiling node-flavored commonjs modules for the browser.
launch a web worker that can require() in the browser with browserify
but also it is extremely easy to transition from browserify to webpack when needed.
If however, you’re predominantly dependent on the NPM ecosystem and you want a tool with a small and very well designed API and takes minimal configuration, you should go for Browserify
We don't particularly need Node compatibility at the moment, but "small and well designed API" is appealing.
On the other hand, not having to hunt around and collect all the tools together for packaging code for the browser is also appealing.
This is probably the best high level comparison of the approach of Webpack and Browserify that I've seen.
Talk from ng-conf 2014 with advice on how to integrate Browserify and Angular, dealing with the fact that both have their own module systems.