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

ts-module-graph

v0.1.0

Published

A modest package for constructing a module graph from TypeScript source files.

Readme

ts-module-graph

A modest package for constructing a module graph from TypeScript source files.

Install

pnpm add ts-module-graph

Usage

import { createModuleGraph } from 'ts-module-graph'
import path from 'node:path'

// The entry points must be absolute paths.
const moduleGraph = await createModuleGraph([path.resolve('src/index.ts')])

// The module graph is a Map of ts.SourceFile objects to ModuleGraphNode objects.
console.log(moduleGraph)

ModuleGraphNode

Each source file has a ModuleGraphNode object associated with it. Each node has the following properties:

  • imports: An array of import objects, each containing information about an import statement.
    • id: The module specifier text (e.g. 'lodash', './my-module')
    • importSpecifiers: An array of ImportSpecifier objects, representing the individual elements being imported.
    • resolvedImports: An array of ResolvedImport objects, providing semantic information about the resolved imports.
    • resolvedModule: A ts.ResolvedModuleFull object, containing information about the resolved module, if available.
  • dependencies: A Set of ts.SourceFile objects, representing the direct dependencies of this module.

ResolvedImport

Each import resolution has the following properties:

  • kind: The kind of import specifier (e.g. 'name', 'namespace', 'default').
  • name: The ts.Identifier representing the imported name.
  • exportName: The ts.ModuleExportName representing the original exported name, if different from the imported name.
  • symbol: The ts.Symbol associated with the imported entity.
  • aliasedSymbol: The original ts.Symbol if the imported symbol is an alias.
  • declarations: An array of ts.Declaration objects where the imported symbol is declared.

ImportSpecifier

Each import specifier has the following properties:

  • kind: The kind of import specifier. Can be:
    • 'name': A named import (e.g. { foo })
      • name: The ts.ModuleExportName representing the imported name.
      • alias: An optional ts.Identifier representing the alias used for the import (e.g. { foo as bar }).
    • 'namespace': A namespace import (e.g. * as foo)
      • name: The ts.Identifier representing the namespace.
    • 'default': A default import (e.g. foo)
      • name: The ts.Identifier representing the default import.

Roadmap

Contribution is welcome to implement these features:

  • [ ] Namespace imports should have their usage tracked to determine which symbols are actually used.
  • [ ] Add a tree-shaking API that whittles down the module graph to only the necessary modules. It doesn't need to be fine-grained; i.e. just filter out modules not used by the entry points (directly or indirectly).

Command-line API

ts-module-graph <...entries>

The entry points are resolved relative to the current working directory. Globs are supported.

This command will print the flattened module graph to the console, using colorization to help with readability.

Thanks

This project wouldn't be possible without these amazing dependencies: