One of the hotter debates in web development as of late revolves around the notion of packaging and sharing reusable components. You may have noticed that many segments of the web development community have stepped up in order to attempt to solve this problem. Interestingly, if you hang around in multiple parts of the community, you’ve probably noticed that there are many solutions being proposed and developed. Unfortunately, these solutions have overlapping and incompatible feature sets, leaving us with a manual integration headache. Don’t get me wrong, there are talented developers working on this problem and I commend their efforts; however, virtually all of them miss a critical detail…
About two years ago, I started looking for the “best client-side script loader”. I even entertained the thought, “perhaps I’ll just write one myself” (famous last words). About a year ago, I started digging further into NodeJS…that is when it all came together and I realized that I should be looking for a client-side “module loader”. You know, npm  for the browser. Little did I know that there was already Ender  and Browserify  in existence. Oh wait, what about that Asset Pipeline  thing or Assetic ? Yes, I frantically tried most of these solutions; and I even wrote about my short list of contenders (http://git.io/_ZWfVA) .
THIS IS A PREVIEW. DOWNLOAD APRIL 2013’S ISSUE TO READ THE FULL ARTICLE.