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

import-cartographer

v0.0.4

Published

Explore the ESM import tree of a file

Readme

import-cartographer

Explore the ESM import tree of a file

Usage

import importer from 'import-cartographer'
// mock compile function
const compile = async name => compileSomeBundle()

const tree = importer(compile)

for await (let [str, location] of tree('./file.js')) {
  if (typeof location === 'string') {
    // local file
  } else {
    location = await location
    // named import, the result comes from the compile function
  }
}

Local files are loaded recursively, so a single tree() call will follow the entire local tree only terminating its recursion at each named import.

For every named import, the compile function is only run once and then cached indefinitely. The same result (most likely a promise from an async function) of the first named import will be emitted for every subsequent import of that name.

This means you can run tree() multiple times on different local files and continue to get the same cached result for any named imports.

const tree = importer(compile)

const run = async filename => {
  for await (let [str, location] of tree('./file.js')) {
    // do stuff
  }
}
const results = await Promise.all([
  run('./test/test-one.js'),
  run('./test/test-two.js')
])

As you can see, you can safely run this concurrently and still be guaranteed to only run each compile function for a named import once.