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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@squareneo/ts-dependency-analysis

v1.0.2

Published

A project for analysing dependencies to members in Typescript code.

Downloads

6

Readme

ts-dependency-analysis

npm npm downloads license TypeScript Node

A CLI and library tool for analysing dependencies to specific entities (interfaces, types, classes, enums, etc.) defined in target TypeScript files. This tool helps you understand how and where your API surface or generated code is referenced throughout your codebase.

Features

  • Configurable Target Files: Specify which files/entities to analyze using glob patterns.
  • Reference Analysis: Find all references to exported interfaces, types, classes, enums, properties, and methods in your target files.
  • Exclusion Support: Exclude files (e.g., tests) from analysis using glob patterns.
  • CLI and Programmatic API: Use as a command-line tool or as a library in your own scripts.
  • JSON Output: Get machine-readable output for further processing.

Installation

npm install -g ts-dependency-analysis

Or as a dev dependency:

npm install --save-dev ts-dependency-analysis

Usage

CLI

ts-dependency-analysis --tsconfig=./tsconfig.json --output=./analysis.json [--targets=pattern] [--exclude=pattern]

Options

  • --tsconfig (required): Path to the TypeScript configuration file.
  • --output (required): Path to the output file (JSON).
  • --targets (optional, repeatable): Glob patterns for target files (default: generated/api files).
  • --exclude (optional, repeatable): Glob patterns to exclude files (default: **/*.spec.ts).
  • --help (optional): Show help message.

Example

ts-dependency-analysis --tsconfig=./tsconfig.json --output=./deps.json --targets=src/api.generated.ts --exclude=**/test/**

Programmatic API

You can use the analysis in your own scripts:

import { analyseDependencies } from "ts-dependency-analysis";

const dependencies = analyseDependencies(
  "./tsconfig.json",
  ["src/api.generated.ts"], // target globs
  ["**/*.spec.ts"] // exclude globs
);
console.log(dependencies);

Output Format

The output is a JSON array of dependency objects:

[
  {
    "name": "MyInterface",
    "kind": "interface",
    "parents": [],
    "originPath": "src/api.generated.ts",
    "references": [
      {
        "filePath": "src/consumer.ts",
        "line": 42,
        "proof": "...code excerpt..."
      }
    ]
  }
  // ...more dependencies
]
  • name: Name of the exported entity.
  • kind: Type of entity (interface, class, type, enum, etc.).
  • parents: Parent namespaces/types (for nested members).
  • originPath: File where the entity is defined.
  • references: List of references with file, line, and code excerpt.

Typical Use Cases

  • API Surface Analysis: Find all usages of your generated API types.
  • Refactoring: Identify where breaking changes will have impact.
  • Documentation: Generate reports of how and where your types are used.

Requirements

  • Node.js >= 16
  • TypeScript >= 5.8