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

dependency-analyser

v1.0.2

Published

Scan your Typescript project for imported and used dependencies and create a statistic as HTML output.

Downloads

3

Readme

dependency-analyser

Scan your Typescript project for imported and used dependencies and create a statistic as HTML output.

Statistics about imported dependencies and used node.js modules: Overview Screenshot

File tree of imported modules: Module Screenshot

Code with a highlighting of import usages: Code Screenshot

Supported imports

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import

[✓] import defaultExport from "module-name";
[✓] import * as name from "module-name";
[✓] import { export1 } from "module-name";
[✓] import { export1 as alias1 } from "module-name";
[✓] import { export1 , export2 } from "module-name"; 
[✓] import { foo , bar } from "module-name/path/to/specific/un-exported/file";
[✓] import { export1 , export2 as alias2 , [...] } from "module-name";
[✓] import defaultExport, { export1 [ , [...] ] } from "module-name";
[✓] import defaultExport, * as name from "module-name";
[✓] import "module-name";  // marked as import, but no highlighting of usages
[✗] var promise = import("module-name");
const module = require("module"); // is not supported

Installing

npm install dependency-analyser

Usage

dependency-analyser [options]

Options:
  --version   Show version number                                      [boolean]
  --root, -r  Root directory of your project.                           [string]
  --scan, -s  Directory to scan. (absolute or relative to root)         [string]
  --tar, -t   Target directory to put generated files into. (absolute or
              relative to root)                                         [string]
  -h, --help  Show help                                                [boolean]

Examples

dependency-analyser --root C:/User/Projects/your_project

dependency-analyser --root C:/User/Projects/your_project
    --scan C:/User/Projects/your_project/src
    --tar "dep analysis"