JSPM: Browser Dependency Management with Import Maps
jspm.org · checked 2 Oct 2026
Browser dependency management built around import maps, with command-line, CDN, API and build tooling.
How it plugs in
Signal on JavaScript Package Managers6.7#1 of 19
JSPM handles browser dependencies with import maps. Its CLI, jspm.io CDN, development server and RollupJS builds support native browser modules and TypeScript type stripping. It works with several package providers, offers a hosted API, and is available as free open-source software. Publishing remains experimental.

Review
In a line
JSPM is an open-source project for browser dependency management using import maps that map module names to package locations. It combines command-line utilities, a CDN and browser-oriented workflows.
What it does
As its primary command-line tool, JSPM CLI handles packages referenced by import maps. Through jspm.io, optimized npm dependencies can be served directly, while Node.js exports and imports, conditional exports and CommonJS-to-ES-module conversion are supported.
The jspm serve command installs packages as needed, reloads changes and removes TypeScript types. For production output, jspm build uses RollupJS to optimize package entry points together with their dependencies. Subresource Integrity hashes can be added to every module in an application's static and dynamic graph.
How it connects
The open-source tooling supports workspaces, lockfiles, peer dependencies, package publishing, offline caches and global installation. Built-in provider choices are jspm.io, nodemodules, esm.sh, unpkg, skypack and jsdelivr, and additional providers may be configured.
Its hosted API can produce import maps and provide static or dynamic dependency graphs for preload generation. JSPM advises using the Generator library locally when feasible, leaving the hosted API as a convenience for environments that cannot readily execute JavaScript. Integrations include an online generator, VSCode web extension, Vite plugin, experimental Node.js loader, Import Map Rails and Symfony AssetMapper.
Good fit
JSPM fits teams developing browser applications with native ES modules and import maps. It is useful when dependencies should come from a CDN, when development needs automatic installation, or when production output should be bundled with RollupJS.
Current Firefox, Safari and Chrome releases, along with Deno, support import maps. JSPM is offered through API, extension, Linux, macOS, self-hosted, web and Windows options.
Watch for
The jspm publish command is experimental, intended for prototyping, and carries no reliability guarantee for publishing on jspm.io. Consider this limitation before including it in a release process.
Import-map support relies on current browser versions or Deno. When JavaScript can run locally, JSPM favors its Generator library over the hosted API. Questions and discussion are handled through Discord.
Pricing
JSPM's open-source package-management project is free, with no paid plan listed.
Verdict
Choose JSPM when browser-native modules, import maps and npm packages delivered by CDN or bundled with RollupJS are central to the work. Its CLI, API, integrations and self-hosted option support different deployment patterns.
If dependable publishing on jspm.io is critical, look elsewhere because jspm publish remains experimental.
Our take
JSPM works well for browser projects using import maps, native ES modules and npm-compatible packages, including setups that want CDN delivery without a separate dependency build. The CLI and development server support day-to-day changes, RollupJS creates production bundles, and the API can produce dependency maps. Publishing is a weaker area because jspm publish is experimental, and teams should verify import-map support in target browsers before adopting it.
- Free, open-source project with import-map package tools
- CDN serves npm dependencies without a separate build step
- Development server supports automatic installation and hot reloading
- Provides workspaces, lockfiles, peer dependencies and offline caching
- Hosted API can produce import maps and dependency graphs
- jspm publish has no reliability guarantee
- Import maps need current Firefox, Safari or Chrome releases, or Deno
- Hosted API is intended mainly for environments unable to run JavaScript
- Pick it ifBrowser applications built with native ES modules and import maps; Teams seeking CDN delivery or RollupJS production bundles; Projects that need self-hosted or command-line package management
- Skip it ifPublishing reliably to jspm.io is a release requirement; Target browsers lack import-map support
Pricing
The JSPM project is free and open source. jspm.io CDN services are free and supported by donations and sponsorships, with no paid plan listed.
- JSPM (open-source project)Open-source import-map package management tools; jspm.io CDN services are described as free and donation-supportedFree
As jspm.org lists them, checked 2 Oct 2026.
Questions
What is JSPM?
JSPM is open-source software for handling browser dependencies through import maps, accompanied by a CLI, CDN, development server and build tooling.
Does JSPM have a free plan?
Yes. The project is free and open source, while jspm.io CDN services are described as free and funded through donations and sponsorships.
What package providers does JSPM support?
The default provider set includes jspm.io, nodemodules, esm.sh, unpkg, skypack and jsdelivr, and custom providers are supported.
Can JSPM build production bundles?
Yes. jspm build uses RollupJS to optimize bundles from package entry points and their dependencies.
Which browsers support JSPM import maps?
Import maps work in current Firefox, Safari and Chrome versions, and in Deno.
Is jspm publish reliable for production?
There is no reliability guarantee; the command is experimental and intended for prototyping on jspm.io.
Does JSPM provide an API?
Yes. The hosted jspm.io API creates import maps and can supply static and dynamic dependency graphs for preload generation.