| People interested in Duo may also want to have a look at jspm.io. It solves a similar problem, but with a few differences which to me are advantages: - Transparently supports modules from CommonJS, AMD, ES6 or globals. - Enforce a manifest (config.js) that let you pin dependencies (incl. transitive dependencies) to exact versions. Unlike RequireJS config, jspm automatically manages that file for you. - Support multiple package providers, e.g. NPM, on top of Github. - Based on SystemJS, a polyfill for the upcoming standard System loader. This hopefully makes it future-proof. - Does not require a compilation step: dependencies can be pulled dynamically from a CDN over SPDY. Alternatively they can be cached locally as well. A compilation step (jspm bundle) is still available. - Works both in the context of Node and the browser. We've been successfully using jspm and SystemJS in production at the Guardian. It's still early days, but the devs are very active and responsive. This isn't meant to distract people away from taking a look at Duo and making up their own mind, but I noticed nobody mentioned jspm in this thread and thought people may want to look at both and compare. |