JSPM

JSPM is an open source project for working with dependency management via import maps in browsers. The jspm.io CDN is the default CDN provider used in the JSPM project for loading optimized dependencies directly from npm without a separate build step.

Import maps enable dynamic linking in the browser, provide a huge caching benefit by treating all URLs as immutable with far-future expires, and maximize cache usage of packages. The jspm.io CDN also has worldwide edge caching, reducing latency and load time.

Yes, JSPM is built entirely around the standards for modules in browsers, the import maps standard, and the Node.js module resolution specification. It extends the Node.js module resolution algorithm in a backwards-compatible way to CDN module resolution.

Yes, jspm.io is designed as a highly available production modules CDN with 99.999% availability. You can track its status at https://status.jspm.io/ and follow the production workflow in the Getting Started guide.

Yes, JSPM is designed to support any CDN providers. You can switch providers using the workflows in the Getting Started guide, and PRs for new providers are welcome to the JSPM Generator core project.

jspm.io is funded through the JSPM Foundation, a member-run Canadian not-for-profit corporation. Donations and sponsorships are used to fund server costs. You can support the project via Open Collective (https://opencollective.com/jspm) or GitHub Sponsors (https://github.com/sponsors/jspm).

No, JSPM does not replace bundling entirely. While it can be possible to skip bundling for simple applications, large applications always require optimization, and bundling remains an important tool in the optimization toolbox.

Browsers can load hundreds of modules in fractions of a second. While highly optimized bundles may be fastest in direct benchmarks, JSPM emphasizes development experience and shared network caching, which can lead to new development and shipping paradigms.