Browserify vs Component

stagas edited this page Apr 11, 2013 · 1 revision

Browserify -vs- Component

This is a comparison of the two biggest CommonJS module managers/bundlers for frontend development. Both have their own pros and cons but they're both useful in their own way. This is meant to highlight some of these traits so you can make an educated choice.

Please edit this page and fix anything I got wrong or forgot to mention.

Feature Browserify Component
Package Manager npm component
Repository npm registry Github
Namespace Single Github username/repo
Local Packages Symlinks "local" in component.json
Local/Private Repositories Hard, need to setup a npm registry Easy, just a static http server emulating GH paths
Module Resolution Directory structure "name" in component.json
Bundler Resolution Automatic using AST, may bundle unnecessary files or miss some Explicit in component.json
Assets Bundling "fs" based, inlined with code Explicit, namespaced, symlinked/copied to public
CSS No Bundled separately in "build.css"
Plugins Yes Yes
SourceMaps Yes No
SourceURLs No Yes
Modular/Hackable Yes Yes
Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.