I was going to suggest the same.<p>JSPM has a lot of really useful characteristics.<p>It includes System.js which is a polyfill for the future ES6-Module-Loader spec. It also supports importing AMD&#x2F;CommonJS modules.<p>JSPM installs modules from the CLI the same way NPM does, except it&#x27;s specifically geared for the client-side. Every module that gets downloaded (incl dependencies) is automatically mapped in a config.js file.<p>JSPM has its own registry but, unlike NPM, the registry is not a requirement. It&#x27;s trivial to install modules directly from GitHub and NPM.<p>The module&#x2F;dependency is flat (NPM is changing to this in V3) so there isn&#x27;t any duplication of dependencies. It also supports multiple versions of a dependency if necessary so there&#x27;s no &#x27;dll hell&#x27; esque issues.<p>JSPM comes built-in with transpiler support for Babel, Traceur, and Typescript. Using them is as simple selecting one of the three during the &#x27;jspm init&#x27; script.<p>It can also be used to build bundles and self-executing bundles (incl minify).<p>The best part is, it aims to directly support the future ES standards while also providing a bridge to use older packaging formats.<p>Browserify and Webpack are extremely popular at the moment but both will inevitably be replaced when the new module standards solidify.