esm.sh
UnclaimedServe NPM packages as modern ES modules directly in browsers and Deno, no build tools needed.
Visit WebsiteFreeVisit Website
TL;DR - esm.sh
- Serves NPM packages as ES modules directly to browsers/Deno.
- Eliminates the need for build tools and local package installations.
- Supports on-the-fly transformation of various file types and dependency management.
Pricing: Free forever
Best for: Individuals & startups
Pros & Cons
Pros
- Simplifies modern web development by removing build steps
- Provides direct access to a vast ecosystem of NPM packages
- Optimizes performance through bundling and tree shaking options
- Supports various module registries for flexibility
Cons
- Reliance on an external CDN for module delivery
- URL-based configuration can become lengthy for complex setups
- Potential for issues if CDN experiences downtime or performance degradation
Key Features
Import NPM packages via HTTP URLsSupport for import mapsSupports NPM, JSR, GitHub, and pkg.pr.new registriesOn-the-fly transformation of .ts(x)/.vue/.svelte filesSpecify and alias dependencies via URL query parametersConfigurable bundling strategies (e.g., ?bundle=false, ?standalone, ?raw)Tree shaking for specific module exports
Pricing
Free
esm.sh is completely free to use with no hidden costs.
About esm.sh
By Toolradar Team·
esm.sh is a fast, smart, and global ESM CDN that allows developers to import NPM packages directly into their web applications or Deno projects using standard JavaScript module syntax. It eliminates the need for local installation, bundling, or complex build processes, simplifying modern web development.
This service supports various registries including NPM, JSR, GitHub, and pkg.pr.new, enabling flexible access to a vast ecosystem of modules. It also offers on-the-fly transformation of .ts(x), .vue, and .svelte files, dependency management through query parameters, aliasing, and configurable bundling strategies to optimize performance and control module behavior. With esm.sh, developers can streamline their workflow, reduce project setup complexity, and leverage the latest JavaScript features directly in the browser.
How we evaluate tools →Source: esm.sh
Reviews
No reviews yet. Be the first to review esm.sh!
Best esm.sh Alternatives
Top alternatives based on features, pricing, and user needs.
Explore More
esm.sh FAQ
How can I specify particular versions for a package's dependencies when importing from esm.sh?
You can specify dependency versions by appending
?deps=PACKAGE@VERSION to the import URL. For multiple dependencies, separate them with commas, like ?deps=react@18.3.1,react-dom@18.3.1.What is the purpose of the `?alias` query parameter in an esm.sh import URL?
The
?alias=PACKAGE:ALIAS parameter allows you to substitute a different package for a dependency. This is useful when you want to use an alternative implementation for a specific dependency within your imported module.How does esm.sh handle bundling of sub-modules, and can I control this behavior?
By default, esm.sh bundles sub-modules not shared by entry modules defined in
package.json's exports field to reduce network requests. You can disable this default bundling by adding ?bundle=false to the import URL or by setting "bundle": false in an esm.sh field within your package.json.Can I import raw JavaScript source code without any transformations from esm.sh?
Yes, you can import the raw JavaScript source code of a package, as-is, without transformation into ES modules by adding the
?raw query to the import URL.What types of registries does esm.sh support for importing modules?
esm.sh supports importing modules from NPM, JSR (using
/jsr/ prefix), GitHub (using /gh/ prefix), and pkg.pr.new (using /pr/ or /pkg.pr.new/ prefixes).Source: esm.sh