JSPM
jspm.org
- Free plan
- Windows
- macOS
- Linux
- Web
- Browser extension
- API
- Self-hosted
What JSPM is
JSPM is an open-source project for managing browser dependencies through import maps. Its CLI is the main tool for working with import-map packages, while the jspm.io CDN loads optimized dependencies from npm without a separate build step. The development server, jspm serve, can install packages automatically, hot-reload, and strip TypeScript types; jspm build uses RollupJS to create optimized production bundles. JSPM supports native ES modules and browser import maps, and can add Subresource Integrity hashes across an application's static and dynamic module graph. Developers can use providers such as jspm.io, nodemodules, esm.sh, unpkg, skypack, and jsdelivr, or configure custom providers. Integrations include a VSCode web extension, Vite plugin, online generator, Import Map Rails, and Symfony AssetMapper. Its hosted API can generate import maps and dependency graphs, though JSPM recommends its Generator library when possible. Import maps are supported in recent Firefox, Safari, and Chrome versions, and in Deno. The project is free; jspm.io services are donation-supported. Publishing through jspm is experimental and carries no reliability guarantees.
Who it suits
JSPM suits developers building browser applications with native ES modules and import maps. It also offers integrations and CDN workflows for teams using the listed frameworks and providers.
Good to know, and what to watch
- CDN loads optimized npm dependencies without a separate build.
- Development server offers automatic installation and hot reloading.
- Production builds use RollupJS.
- Supports Subresource Integrity hashes for module graphs.
- Free and open source.
- jspm publish is experimental without reliability guarantees.
- JSPM recommends its Generator library over the hosted API where possible.
Plans
Every plan and priceJSPM (open-source project)
Open source
Getting started
- Visit https://jspm.org/ for the project and its documentation.
- Global installation of the JSPM CLI is supported for managing import maps from the command line.
- Use the online generator or select a default or custom provider for dependencies.
- Use jspm serve for development, or jspm build for production bundles.
- For questions and discussion, join the JSPM Discord.
The Club's review
Overview
JSPM is an open-source package-management project for browser dependencies, built around import maps and native ES modules. It is best suited to developers who want npm packages in standards-based browser workflows, with the option to bundle for production. Its main caveat is clear: package publishing through jspm.io is experimental, not a dependable production path.
Key features
The JSPM CLI manages import maps, while the jspm.io CDN loads optimized dependencies from npm without requiring a separate build step. Support for Node.js package exports, conditional exports, and CommonJS-to-ES-module conversion makes a broader range of packages usable in browser applications. The CDN also performs RollupJS code-splitting optimization and serves source maps.
For development, jspm serve can install packages automatically, hot reload changes, and strip TypeScript types. For production, jspm build uses RollupJS to bundle package entry points and dependencies. This makes JSPM useful for teams that want to begin with direct browser imports but retain a bundling route when deployment needs it.
JSPM can add Subresource Integrity hashes across an application's static and dynamic module graph, a practical safeguard for applications loading dependencies through modules. Its hosted API generates import maps and can return dependency graphs for preload generation. JSPM recommends running the Generator library directly where possible; the API is a convenience for environments that cannot readily run JavaScript.
Default providers include jspm.io, nodemodules, esm.sh, unpkg, skypack, and jsdelivr, and custom providers can be configured. Official integrations include an online generator, a VSCode web extension, a Vite plugin, an experimental Node.js loader, Import Map Rails, and Symfony AssetMapper. That range helps JSPM fit existing workflows, though the Node.js loader itself is experimental.
Import maps work in the latest versions of Firefox, Safari, and Chrome, as well as in Deno. The jspm.io CDN reports redundant storage and caching layers and 99.99% historical uptime. That is a useful availability record, but the separate experimental publishing command has no reliability guarantees and is intended only for prototyping.
Pricing
JSPM (open-source project): free. The plan provides open-source import-map package-management tools; jspm.io CDN services are free and funded through donations and sponsorships. There are no paid tiers or usage limits stated for the project, so it suits individual developers and teams that want an open-source workflow without a software subscription.
JSPM is funded through the JSPM Foundation, a member-run Canadian not-for-profit corporation, with donations and sponsorships supporting server costs. Users can ask questions and discuss the project on Discord. The Open Collective lists priority support as a sponsor benefit.
Platforms
JSPM is available as an API, extension, web service, and for Linux, macOS, Windows, and self-hosted use. Its browser-centered workflow is most relevant to applications using import maps and native ES modules; compatibility depends on current browser support for import maps.
Who it's for
Choose JSPM if your application is built around browser modules and you want to manage npm dependencies through import maps, with development-server support and an optional production bundling path. Its CDN and provider choices suit teams that want to load dependencies without a mandatory local build step. Look elsewhere if reliable package publishing through jspm.io is a core requirement, or if your project does not use browser import maps.
Pros and cons
Pros
- Flexible browser workflow: Direct CDN imports, development tooling, and RollupJS production builds support different stages without requiring one fixed approach.
- Broad package handling: Node.js exports, conditional exports, and CommonJS conversion extend compatibility with npm packages.
- Integrity support: Subresource Integrity hashes can cover both static and dynamic module graphs.
- Open source and free: The project and CDN services are free, with server costs supported by donations and sponsorships.
Cons
- Publishing is not production-ready: The experimental publish command has no reliability guarantees and is intended for prototyping.
- Import maps are a prerequisite: The workflow fits browser-native module projects, not every JavaScript package-management need.
- Hosted API is not the preferred route when JavaScript is available: JSPM recommends running its Generator library directly where possible.
Alternatives
npm is a better fit for public package authors who need public package publishing and registry access; its free plan allows unlimited public packages.
Pantry is another freemium option for public packages, with a free plan that includes 30 days of full analytics, 50MB of artifacts, and a standard build queue.
Deno Sandbox suits readers looking for a hosted sandbox API or web platform, with a free plan that includes 1M requests per month and 10 hours of active CPU.
vlt is worth considering for a self-hosted or web package-management option; its free plan includes 2GB of storage and delivery, an upstream proxy, user and token management, and community support.
Yarn, Rush, pnpm, and Utoo are other options to compare.
For a broader comparison, see JavaScript Package Managers.
Verdict
JSPM is a strong choice for developers building browser applications with native ES modules who want import-map dependency management, CDN delivery, and an optional production build path in an open-source project. Its focused browser workflow is the main reason to choose it; if dependable package publishing is essential, use another publishing path or choose a different tool.
The verdict
JSPM brings dependency management, development, and production bundling into import-map workflows. Its publishing command is explicitly experimental, so it is not a reliable publishing path.
Questions people ask
How much does JSPM cost?
The open-source project is free: its listed plan is free. The jspm.io CDN services are described as free and donation-supported.
Which browsers support import maps?
Import maps are supported in the latest versions of Firefox, Safari and Chrome, and in Deno.
Can JSPM create production bundles?
Yes. jspm build uses RollupJS to create optimized bundles from package entry points and dependencies.
Can JSPM publish packages reliably to jspm.io?
The publish command is experimental and has no reliability guarantees for publishing on jspm.io.
What integrations does JSPM offer?
Official integrations include an online generator, a VSCode web extension, a Vite plugin, an experimental Node.js loader, Import Map Rails and Symfony AssetMapper.
Where can users get help?
JSPM directs users to its Discord for questions and further discussion.
What the maker publishes
- API
- The hosted jspm.io API generates import maps and can return static and dynamic dependency graphs for preload generation. source
- API guidance
- JSPM recommends running the Generator library directly when possible and positions the hosted API as a convenience for environments that cannot readily run JavaScript. source
- Availability
- The jspm.io CDN page reports 99.99% historical uptime and links to its status page. source
- Browser workflow
- JSPM supports native ES modules, import maps, TypeScript type stripping and standards-based browser workflows. source
- CDN
- The jspm.io CDN loads optimized dependencies directly from npm without a separate build step. source
- CDN
- The jspm.io CDN serves optimized and minified packages with source maps and versioned URLs. source
- CDN availability
- The jspm.io CDN page reports redundant storage and caching layers with 99.99% historical uptime. source
- CDN optimization
- jspm.io performs RollupJS code-splitting optimization and serves source maps. source
- CLI
- The JSPM CLI is the main command-line import map package management tool. source
- CLI
- The JSPM CLI installs, updates, and manages dependencies in import maps. source
- Compatibility
- Import maps are supported in the latest versions of Firefox, Safari and Chrome, and in Deno. source
- Development server
- jspm serve provides auto-installation, hot reloading and TypeScript type stripping. source
- Development server
- The CLI development server supports automatic import-map updates, live reload, and TypeScript type stripping. source
- Funding
- jspm.io is funded through the JSPM Foundation, a member-run Canadian not-for-profit corporation, with donations and sponsorships funding server costs. source
- Funding and support
- The project says donations and sponsorships fund server costs, and its Open Collective lists priority support as a sponsor benefit. source
- Integrations
- Official integrations include an online generator, a VSCode web extension, a Vite plugin, an experimental Node.js loader, Import Map Rails and Symfony AssetMapper. source
- Integrations
- JSPM documents an online generator, a VS Code web extension, a Vite plugin, and integrations for Rails and Symfony AssetMapper. source
- Notable limit
- JSPM says its publish command is experimental and intended only for prototyping, without reliability guarantees for publishing on jspm.io. source
- Package compatibility
- The CDN supports Node.js package exports and imports, conditional exports, and conversion of CommonJS modules to ES modules. source
- Production builds
- jspm build uses RollupJS to create optimized bundles from package entry points and dependencies. source
- Production builds
- JSPM can build packages and dependencies with RollupJS and generate production import maps with integrity hashes and preload tags. source
- Providers
- JSPM supports jspm.io, nodemodules, esm.sh, unpkg, skypack and jsdelivr providers by default, with custom providers configurable. source
- Providers
- Documented package providers include jspm.io, local node_modules, esm.sh, unpkg, skypack, and jsdelivr. source
- Publishing limitation
- The jspm publish command is experimental and has no reliability guarantees for publishing on jspm.io. source
Checked against the maker's pages on 2 Oct 2026.