When comparing JSPM vs stealjs, the Slant community recommends JSPM for most people. In the question“What are the best frontend JavaScript module bundlers?” JSPM is ranked 7th while stealjs is ranked 10th. The most important reason people chose JSPM is:
JSPM is registry agnostic, it can pull packages from npm and github and is built in such a way it can support more.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Registry agnostic
JSPM is registry agnostic, it can pull packages from npm and github and is built in such a way it can support more.
Pro Module style agnostic
Loads ES6, AMD, CommonJS and globals.
Pro Can transcompile ES6, JSX and Typescript
Pro Much faster than Webpack or Browserify
While Webpack and Browserify recompile the source code using Babel, jspm is the only packager that can load prebuild/minified code downloaded from the npm registry.
Pro Bundled based on imported modules without any config
Create the bundle file without config and add only the modules imported.
Pro Switch between async or sync load
With a simple command you could change between load the modules async by systemjs or sync with a bundle file.
Pro Easy install packages from npm, github or any git repository
Pro Versioned package urls
It creates a packages folders which are versioned. This makes it future proof for a time where we stop bundling all the code. In the following presentation Guy Bedford calls bundling an anti-pattern.
Pro Very easy to start with
Pro Supports several modules types
StealJS has support for AMD, CJS and ES6 module types.
Pro Support for LESS and CSS
StealJS can also load CSS and LESS files in addition to JavaScript modules.
Pro Mix ES6 AMD and CommonJS
StealJS supports using all three module types, even in the same file.
Pro ES6 module support
StealJs supports ES6 modules and their import
and export
methods without having to compile them to CommonJS require
.
Pro Support for ES6
StealJS supports transpiling of ES6 code to ES5
Pro Supports all systemjs based plugins
Pro Supports source maps for easier debugging
Source maps allow for easier debugging, because they allow you to find the problems within the origin files instead of the output file.
Pro Share the same modules client-side and server-side
Because StealJS allows you to use the same require()
function as node.js, you can easily share modules between the client-side and server-side.
Pro Tap into npm's huge module ecosystem
Using StelaJS opens you up to npm, that has over 80k modules of which a great amount work both client-side and server-side. And the list is growing rapidly.
Cons
Con You need to be an expert to write shims
You can load any module. But that comes with the price:
you need to find or write configs to load a particular rare module.
Con Doesn't hide complexity
JSPM doesn't try to hide complexity from the user. I.e. when some issue emerges you need understand a lot to be able to patch it or create a workaround.
Con Watcher has bugs
Watching would benefit from improvements
Con Unstable API
0.17 is still in beta. 0.16 is lacking features.
Con Poor bundler performance
Bundling performance is slow, though offset by the fact that bundling is not required during development, since it can load dependencies asynchronously.
Con Changing the order of require statements causes unexpected behavior
Sometimes changing the order of the require
statements in a JavaScript file loaded with stealjs may cause unexpected problems or even breaking the code altogether.