Tuesday 2nd April, 2013
5:00pm to 5:50pm
One of Node.js's most important features is its package manager, npm. It's widely lauded for its successful model of local dependencies, small and focused packages, and the ecosystem it has encouraged. But what about the browser? What about HTML5 “packages”?
There have been a number of ill-fated attempts to solve this problem over the years, but none have reached critical mass. Browser package registries sputter along at a hundred, maybe a thousand packages, mostly written by a small cadre of authors invested in that particular packaging solution. But recently, the obvious solution has become hard to ignore: just use npm itself!
Given Node.js's focus on small packages, it's no wonder that many packages in npm work equally well in the browser. And a growing number of authors are publishing their client-side components to npm as well. This talk discusses how npm's standardized format, with a package.json and CommonJS modules, is actually perfect for browser use, and how I and others have used it successfully on several large enterprise-scale projects.This has impressive implications for code reuse between projects, as well: once client-side package management becomes as simple as that of Node.js, it becomes much easier to decouple your application into separate reusable packages that can be shared among projects or even open-sourced.
Sign in to add slides, notes or videos to this session