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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@dependents-tracker/extractor

v0.1.1

Published

A CLI tool to extract dependents of a given repository.

Downloads

34

Readme

@dependents-tracker/extractor

The CLI tool collects dependents information for a given repository as follows:

  • Collects the dependents of a given repository from the GitHub Dependents Page.
  • Collects the import statements from the source code of the dependents repositories.

Finally, it generates a JSON file with the following structure:

{
  "repository_name": {
    "imports": [
      {
        "filename": "/path/to/file",
        "specifiers": ["imported_module", "imported_module2"]
      }
    ],
    "hash": "3d129uasf...",
  }
  ...
}

One more thing to note is that it can collect javascript projects that use the ESM-style imports, which means that it does not collect the CommonJS-style imports or python projects, etc. It also can't collect the default imports.

// OK
import { foo } from 'bar';

// NOT OK
const foo = require('bar');
import foo from 'bar';

And it runs in concurrent mode, so it can collect the dependents faster.

Prerequisites

  • git installed on your machine.
  • node installed on your machine.
  • npm installed on your machine.

Usage

npx @dependents-tracker/extractor <repository_name> [<file_path of `result.json`>]

At now, the CLI tool only supports above command. The repository_name should be in the format of owner/repo. And If you have a previously generated result.json file, you can pass the file path as the second argument. Then the CLI tool will use the existing data and only collect the new dependents.

After running the command, the CLI tool will generate a JSON file in the current directory with the name result.json.

Note: This project is still under development, so there might be some bugs or issues. If you encounter any, please report them.