Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Gourmet vs JSPM, the Slant community recommends JSPM for most people. In the question“What are the best client-side JavaScript module loaders?” JSPM is ranked 4th while Gourmet is ranked 9th. 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.
Question Ranking
Pros
Pro Friendly asset handling
Auto-asset inclusion, native CSS support, and flexible bundling make handling your assets simple.
Pro ES6 support
Supports ES6 syntax by default.
Pro Easy configuration
Declarative configuration makes project setup easy.
Pro Isomorphic rendering by default
The runtime environment allows for isomorphic rendering of React applications by default.
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
Cons
Con Feature set is unclear
Con Not available yet
Con Zero documentation
Con Browser support unknown
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.
