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

pkg-usage

v0.4.1

Published

Npm package usage metrics

Downloads

6

Readme

📦 pkg-usage

npm

Installation

npm install pkg-usage

# or

yarn add pkg-usage

Introduction

Have you ever wondered how your library is being used in other repositories? It's your lucky day because this package aims to solve it.

Given a few options you can gets details about how your library is being imported along with its version

Usage

import { getPackagesUsages } from 'pkg-usage';

const usages: PackageUsage[] = getPackagesUsages({
  packages: ['react'],
  fileGlobs: `**/**.ts`,
  packageJsonCWD: './package.json',
  analyzeImportUsages: false,
});

console.log(usages);

Package Usage types

export type JSXElementUsage = {
  line: number;
  props: string[];
  text: string;
};

export type CallExpressionUsage = {
  line: number;
  text: string;
};

export type ValueUsage = {
  line: number;
  text: string;
};

export type PropertyAccessExpressionUsage = {
  line: number;
  property: string;
  text: string;
};

export type Usages =
  | JSXElementUsage[]
  | (CallExpressionUsage | PropertyAccessExpressionUsage | ValueUsage)[];

export type Import = {
  name: string;
  type: ExportType;
  usages?: Usages;
};

export type FileUsage = {
  name: string;
  filePath: string;
  imports: Import[];
};

export type PackageUsage = {
  name: string;
  count: number;
  files?: FileUsage[];
  version?: string;
};

CLI usage

| Options | Description | Example | | --------------------------- | ------------------------------------- | ---------------------------------------------- | | -p, --packages | Packages to analyze | -p vue,vuex or --packages="react,redux" | | -f, --file-globs | Files to analyze based on file globs | -f ".(ts|tsx)" or --file-globs=".(js|jsx)" | | -u, --analyze-import-usages | (Experimental) Analyzes import usages | -u | | -cwd, --package-json-CWD | Directory to start from | -cwd "/path/to/start/from" |

npx

npx is a package runner tool

npx pkg-usage -p "react,redux" -f "**/*.(ts|tsx)"

Or

npx pkg-usage --packages="vue,vuex" --file-globs="**/*.(js|vue)"

If you use npm 5.1 or earlier, you can't use npx. Instead, install it globally:

npm install -g pkg-usage

Now you can run:

pkg-usage -p "react,redux" --f "**/*.(ts|tsx)"