esm.sh allows you to import JavaScript modules from http URLs, no installation/build steps needed.

import * as mod from "https://esm.sh/PKG[@SEMVER][/PATH]";

With import maps, you can even use bare import specifiers instead of URLs:

<script type="importmap">
  {
    "imports": {
      "react": "https://esm.sh/react@19.1.0",
      "react-dom/": "https://esm.sh/react-dom@19.1.0/"
    }
  }
</script>
<script type="module">
  import React from "react"; // → https://esm.sh/react@19.1.0
  import { render } from "react-dom/client"; // → https://esm.sh/react-dom@19.1.0/client
</script>

More usages about import maps can be found in the Using Import Maps section.

Supported Registries

• NPM:

  // Examples
  import React from "https://esm.sh/react"; // latest
  import React from "https://esm.sh/react@18"; // 18.2.0
  import React from "https://esm.sh/react@next"; // next tag
  import { renderToString } from "https://esm.sh/react-dom/server"; // sub-modules
  

• JSR (starts with /jsr/):

  // Examples
  import { encodeBase64 } from "https://esm.sh/jsr/@std/encoding@1.0.0/base64";
  import { Hono } from "https://esm.sh/jsr/@hono/hono@4";
  

• GitHub (starts with /gh/):

  // Examples
  import tslib from "https://esm.sh/gh/microsoft/tslib"; // latest
  import tslib from "https://esm.sh/gh/microsoft/tslib@d72d6f7"; // with commit hash
  import tslib from "https://esm.sh/gh/microsoft/tslib@v2.8.0"; // with tag
  

• pkg.pr.new (starts with /pr/ or /pkg.pr.new/):

  // Examples
  import { Bench } from "https://esm.sh/pr/tinylibs/tinybench/tinybench@a832a55";
  import { Bench } from "https://esm.sh/pr/tinybench@a832a55"; // --compact
  

Transforming .ts(x)|.vue|.svelte on the Fly

esm.sh allows you to import .ts(x), .vue, and .svelte files directly in the browser without any build steps.

import { Airplay } from "https://esm.sh/gh/phosphor-icons/react@v2.1.5/src/csr/Airplay.tsx?deps=react@19.1.0";
import IconAirplay from "https://esm.sh/gh/phosphor-icons/vue@v2.2.0/src/icons/PhAirplay.vue?deps=vue@3.5.8";

Specifying Dependencies

By default, esm.sh rewrites import specifiers based on the package dependencies. To specify the version of these dependencies, you can add ?deps=PACKAGE@VERSION to the import URL. To specify multiple dependencies, separate them with commas, like this: ?deps=react@18.2.0,react-dom@18.2.0.

import React from "https://esm.sh/react@18.2.0";
import useSWR from "https://esm.sh/swr?deps=react@18.2.0";

Aliasing Dependencies

You can also alias dependencies by adding ?alias=PACKAGE:ALIAS to the import URL. This is useful when you want to use a different package for a dependency.

import useSWR from "https://esm.sh/swr?alias=react:preact/compat";

in combination with ?deps:

import useSWR from "https://esm.sh/swr?alias=react:preact/compat&deps=preact@10.10.0";

Bundling Strategy

By default, esm.sh bundles sub-modules of a package that are not shared by entry modules defined in the exports field of package.json.

Bundling sub-modules can reduce the number of network requests, improving performance. However, it may result in repeated bundling of shared modules. In extreme cases, this can break package side effects or alter the import.meta.url semantics. To prevent this, you can disable the default bundling behavior by adding ?bundle=false:

import "https://esm.sh/svelte?bundle=false";

For package authors, it is recommended to define the exports field in package.json. This specifies the entry modules of the package, allowing esm.sh to accurately analyze the dependency tree and bundle the modules without duplication.

{
  "name": "foo",
  "exports": {
    ".": {
      "import": "./index.mjs",
      "types": "./index.d.ts"
    },
    "./submodule": {
      "import": "./submodule.mjs",
      "types": "./submodule.d.ts"
    }
  }
}

Or you can override the bundling strategy by adding the esm.sh field to your package.json:

{
  "name": "foo",
  "esm.sh": {
    "bundle": false // disables the default bundling behavior
  }
}

You can also add the ?standalone flag to bundle the module along with all its external dependencies (excluding those in peerDependencies) into a single JavaScript file.

import { Button } from "https://esm.sh/antd?standalone";

Tree Shaking

By default, esm.sh exports a module with all its exported members. However, if you want to import only a specific set of members, you can specify them by adding a ?exports=foo,bar query to the import statement.

import { __await, __rest } from "https://esm.sh/tslib"; // 7.3KB
import { __await, __rest } from "https://esm.sh/tslib?exports=__await,__rest"; // 489B

By using this feature, you can take advantage of tree shaking with esbuild and achieve a smaller bundle size. Note, this feature doesn't work with CommonJS modules.

Development Build

import React from "https://esm.sh/react?dev";

With the ?dev query, esm.sh builds a module with process.env.NODE_ENV set to "development" or based on the condition development in the exports field. This is useful for libraries that have different behavior in development and production. For example, React uses a different warning message in development mode.

ESBuild Options

By default, esm.sh checks the User-Agent header to determine the build target. You can also specify the target by adding ?target, available targets are: es2015 - es2024, esnext, deno, denonext, and node.

import React from "https://esm.sh/react?target=es2022";

Other supported options of esbuild:

• Conditions

  import foo from "https://esm.sh/foo?conditions=custom1,custom2";
  

• Keep names

  import foo from "https://esm.sh/foo?keep-names";
  

• Ignore annotations

  import foo from "https://esm.sh/foo?ignore-annotations";
  

CSS-In-JS

esm.sh supports importing CSS files in JS directly:

<link rel="stylesheet" href="https://esm.sh/monaco-editor?css">

This only works when the package imports CSS files in JS directly.

Web Worker

esm.sh supports ?worker query to load the module as a web worker:

import createWorker from "https://esm.sh/monaco-editor/esm/vs/editor/editor.worker?worker";

// create a worker
const worker = createWorker();
// rename the worker by adding the `name` option for debugging
const worker = createWorker({ name: "editor.worker" });
// inject code into the worker
const worker = createWorker({ inject: "self.onmessage = (e) => self.postMessage(e.data)" });

You can import any module as a worker from esm.sh with the ?worker query. Plus, you can access the module's exports in the inject code. For example, use the xxhash-wasm to hash strings in a worker:

import createWorker from "https://esm.sh/xxhash-wasm@1.0.2?worker";

// variable '$module' is the imported 'xxhash-wasm' module
const inject = `
const { default: xxhash } = $module
self.onmessage = async (e) => {
  const hasher = await xxhash()
  self.postMessage(hasher.h64ToString(e.data))
}
`;
const worker = createWorker({ inject });
worker.onmessage = (e) => console.log("hash is", e.data);
worker.postMessage("The string that is being hashed");

The inject parameter must be a valid JavaScript code, and it will be executed in the worker context.

Deno Compatibility

esm.sh is a Deno-friendly CDN that resolves Node's built-in modules (such as fs, os, net, etc.), making it compatible with Deno.

import express from "https://esm.sh/express";

const app = express();
app.get("/", (req, res) => {
  res.send("Hello World");
});
app.listen(3000);

Deno supports type definitions for modules with a types field in their package.json file through the X-TypeScript-Types header. This makes it possible to have type checking and auto-completion when using those modules in Deno. (link).

In case the type definitions provided by the X-TypeScript-Types header is incorrect, you can disable it by adding the ?no-dts query to the module import URL:

import unescape from "https://esm.sh/lodash/unescape?no-dts";

This will prevent the X-TypeScript-Types header from being included in the network request, and you can manually specify the types for the imported module.

Import Maps has been supported by most modern browsers and Deno natively. This allows bare import specifiers, such as import React from "react", to work.

esm.sh introduces the ?external for specifying external dependencies. By employing this query, esm.sh maintains the import specifier intact, leaving it to the browser/Deno to resolve based on the import map. For example:

<script type="importmap">
{
  "imports": {
    "preact": "https://esm.sh/preact@10.10.0",
    "preact/": "https://esm.sh/preact@10.10.0/",
    "preact-render-to-string": "https://esm.sh/preact-render-to-string@6.5.0?external=preact"
  }
}
</script>
<script type="module">
  import { h } from "preact";
  import { useState } from "preact/hooks";
  import { render } from "preact-render-to-string";
</script>

Alternatively, you can mark all dependencies as external by adding a * prefix before the package name:

{
  "imports": {
    "preact": "https://esm.sh/preact@10.10.0",
    "preact-render-to-string": "https://esm.sh/*preact-render-to-string@6.5.0",
    "react": "https://esm.sh/preact@10.10.0/compat",
    "swr": "https://esm.sh/*swr@1.3.0" // preact/compat is imported instead of react
  }
}

Import maps supports trailing slash that can not work with URL search params friendly. To fix this issue, esm.sh provides a special format for import URL that allows you to use query params with trailing slash: change the query prefix ? to & and put it after the package version.

{
  "imports": {
    "react-dom": "https://esm.sh/react-dom@19.1.0?dev",
    "react-dom/": "https://esm.sh/react-dom@19.1.0&dev/"
  }
}

esm.sh/tsx is a lightweight 1KB script that allows you to write TSX directly in HTML without any build steps. Your source code is sent to the server, compiled, cached at the edge, and served to the browser as a JavaScript module.

esm.sh/tsx supports <script> tags with type set to text/babel, text/jsx, text/ts, or text/tsx.

In development mode (open the page on localhost), esm.sh/tsx uses @esm.sh/tsx to transform JSX syntax into JavaScript.

<!DOCTYPE html>
<html>
<head>
  <script type="importmap">
    {
      "imports": {
        "react": "https://esm.sh/react@19.1.0",
        "react-dom/client": "https://esm.sh/react-dom@19.1.0/client"
      }
    }
  </script>
  <script type="module" src="https://esm.sh/tsx"></script>
</head>
<body>
  <div id="root"></div>
  <script type="text/babel">
    import { createRoot } from "react-dom/client"
    createRoot(root).render(<h1>Hello, World!</h1>)
  </script>
</body>
</html>

By default, esm.sh transforms your JSX syntax with jsxImportSource set to react or preact which is specified in the importmap. To use a custom JSX runtime, add @jsxRuntime specifier in the importmap script. For example, solid-js.

Which browsers are supported?

esm.sh supports all modern browsers which support ES6 Module. Including Deno.

Does esm.sh support private npm packages?

Nope, but you can deploy your own esm.sh server to support private npm packages. Check our self hosting guide.

Why I get timeout error?

When first time you import a module, esm.sh needs to build the module then cache it. If the module is too large, it may take a long time to build. You can try again later, since it's queued and will be built soon.

Does esm.sh support Subresource Integrity (SRI)?

Browsers don't yet support SRI for ES6 Module. Deno (1.18+) supports hash check by generating the deno.lock file.

How can I report a bug?

Please open an issue on GitHub. Thanks :)