JSPM is making some terrible choices IMO.
-
Doesn't use npm the CLI, instead it uses NPM the http registry
there is a very high chance that developers using JSPM also use NPM. Now their NPM packages might get installed in
node_modules
orjspm_packages
even though they are the same package. They also need to understand how the jspm npm-registry works if anything goes wrong even though they already know how NPM works.there are
goodreasons they are doing this... but I am not convinced those reasons are worth it. In other words, I would rather see more complexity in JSPM to abstract this way, than more complexity on the consumer (as noted above). -
Uses both git the CLI and github's http api for the git registry