esm-dev/esm.sh

A no-build JavaScript CDN for modern web development.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 24 seconds ago
Added to GitGenius on September 16th, 2026
Created on September 6th, 2020
Open Issues & Pull Requests: 314 (+0)
GitHub issues: Enabled
Number of forks: 209
Total Stargazers: 4,176 (+0)
Total Subscribers: 16 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.5 hours
Mean response time: 42.0 days
90th percentile: 51.9 days
Tracked items: 225

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 55% of issues opened in the past year have been closed. Three people close 78% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 140
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 525 days
Stale 30+ days: 137
Stale 90+ days: 135

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 1

Top labels

  • browser (115)
  • deno (53)
  • types (7)
  • bug (5)

Most active issues this week

Detailed Description

esm.sh is a no-build JavaScript CDN that serves ES modules directly to browsers without requiring a build step.

The tool solves the problem of managing JavaScript dependencies in web projects by hosting npm packages as ready-to-use ES modules. Instead of bundling code locally or relying on traditional package managers, developers can import packages directly from a CDN URL in their HTML or JavaScript files. The service automatically transforms npm packages into ES module format and handles dependency resolution on the fly, eliminating the need for build tools like webpack or esbuild for many projects.

The tool suits developers building modern web applications who want to avoid build complexity, particularly for small projects, prototypes, or scenarios where a no-build workflow is preferable. It works well for importing individual packages without local installation and is especially valuable when rapid iteration matters more than optimizing bundle size. Teams should consider it when they want to reduce tooling overhead while still accessing the full npm ecosystem.

Development activity shows consistent engagement with the codebase. The project receives regular updates addressing functionality and compatibility. Pull requests are reviewed and merged steadily, indicating active maintenance. Issues are addressed with reasonable responsiveness, and the maintainers respond to user feedback and bug reports. The project demonstrates sustained attention to keeping the service reliable and compatible with evolving JavaScript standards and npm package changes.