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

@brkncookie/dependency_analyzer

v1.0.1

Published

analyzes a NodeJS project's dependency-graph for circular dependencies and dependency conflicts.

Downloads

13

Readme

dependency_analyzer

dependency_analyzer is a CLI tool written in TypeScript to help you find dependency conflicts and circular dependencies in your NodeJS projects. It analyzes the dependencies as described in the package.json of your NodeJS project.

Features

  • Detects dependency conflicts in your project.
  • Identifies circular dependencies among your project dependencies.
  • Provides a detailed analysis based on the package.json file.

Installation

Install dependency_analyzer globally using npm:

$ npm install -g @brkncookie/dependency_analyzer

Or clone this repo and use the link script:

$ git clone https://github.com/brkncookie/dependency_analyzer
$ cd dependency_analyzer && npm install && npm run link

Usage

Run dependency_analyzer in the root directory of your NodeJS project:

$ dependency_analyzer
### Dependency Conflicts:


1. **Conflict 1:**
   - Package Name: combined-stream
   - First Dependent: Main Project
     - Required Version: 1.0.0
   - Second Dependent: axios -> form-data
     - Required Version: 1.0.8


2. **Conflict 2:**
   - Package Name: delayed-stream
   - First Dependent: combined-stream
     - Required Version: 0.0.5
   - Second Dependent: axios -> form-data -> combined-stream
     - Required Version: 1.0.0


### Circular Dependencies:


1. **Circular Dependency 1:**
   - First Package: combined-stream
   - Second Package: delayed-stream
   - Direct: Yes

Explanation of the above output

this is the dependencies property part of our package.json:

 "dependencies": {
    "combined-stream": "1.0.0",
    "axios": "1.7.2"
  }

as can be seen our main project depends on two packages:

  • combined-stream
  • axios

the problem here is that the axios package itself dependes on a different version of the combined-stream package thus resulting in a dependency conflict, and if the two different versions of combined-stream also have their own dependencies they may result in a deep dependency conflict as it is the case for the delayed-stream package which is a dependency of the combined-stream package.

we also have an intentionally made direct circualr dependency (by manually modifying the lockfile) between combined-stream and delayed-stream.