npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@kayahr/importmap

v0.1.0

Published

Import map generator for installed Node.js packages

Readme

Importmap

GitHub | NPM | API doc

A small tool which generates browser import maps from the packages installed in node_modules.

Features

  • Maps the current package and all installed runtime dependencies, including transitive dependencies.
  • Also maps the current package's installed development dependencies when --dev option is used.
  • Adds import-map scopes when nested node_modules contain different package versions.
  • Supports package exports, relative package imports, trailing-wildcard subpaths and the legacy module, jsnext:main, browser and main fields.
  • Selects browser, import and default export conditions, plus development when --dev option is used.
  • Writes either plain JSON or a browser script which injects the import map with correctly rebased URLs.
  • Has no runtime dependencies.

Usage

Install the tool as a development dependency:

npm install --save-dev @kayahr/importmap

Generate a JavaScript import map for the runtime dependencies of the package in the current directory:

npx @kayahr/importmap lib/importmap.js

The output format is selected from the filename. Use .json for plain JSON:

npx @kayahr/importmap lib/importmap.json

Add --dev (or -D) to include development dependencies:

npx @kayahr/importmap --dev lib/importmap.js

A typical package.json script looks like this:

{
    "scripts": {
        "build:importmap": "importmap lib/importmap.js"
    }
}

JavaScript output can be loaded directly before the first module script. It injects an inline import map immediately after itself:

<script src="lib/importmap.js"></script>
<script type="module" src="lib/main.js"></script>

Unfortunately, browsers currently support import maps only as inline JSON inside <script type="importmap">; they cannot load an external JSON import map through src. This is exactly why the JavaScript output uses an injection wrapper: The wrapper can be loaded as a classic external script, rebases the mappings to its own URL and injects the embedded JSON as an inline import map. Plain JSON output contains the same mappings without this wrapper and is primarily intended for tooling or manual inline embedding. All addresses are relative to the generated file.

API

The same functionality is available as an ESM API:

import { writeImportMap } from "@kayahr/importmap";

await writeImportMap("lib/importmap.json", {
    projectDirectory: ".",
    dev: false
});