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

depstatus

v1.1.1

Published

Simple, synchronous way to get a status check on installed dependencies

Downloads

13,751

Readme

depStatus

A simple, synchronous way to get a status check on installed Node.js dependencies

Perhaps you need to know whether your project's packages are correctly installed, or are out of date, or maybe even are ahead in time (from working in a branch, for example), or just have something funky going on. Try depStatus!

Unlike other dependency status checkers, depStatus:

  • Runs synchronously and quite quickly
  • Only has a single dependency: semver
  • Has full support for prerelease package versions (e.g. "a-package": "^2.0.0-RC.1")
  • Also supports NPM tag pinning (e.g. "a-package": "latest")
  • Even supports packages installed via archive (.tar, .tar.gz, .tgz) and git (npm i https://someurl.com/repo.git
  • Respects and uses package-lock.json if present (but does not depend on it)

Installation

npm i depstatus

Usage

depStatus accepts two parameters:

  • dir: String file path containing a package.json file
  • options: Object options; named parameter time will console log the amount of time it took to run each dependency check

Example:

let depStatus = require('depstatus')
let dir = '/a/dir/to/check' // must contain package.json
let result = depStatus(dir)

depStatus returns the following object:

{
  ok: [
    {
      'an-ok-dependency': {
        versionSpecified: '1.0.0',
        versionInstalled: '1.0.0'
      }
    }
  ],
  missing: [
    {
      'a-dep-not-yet-installed': {
        versionSpecified: '1.0.0',
        versionInstalled: null
      }
    }
  ],
  outdated: [
    {
      'an-outdated-dependency': {
        versionSpecified: '1.0.0',
        versionInstalled: '0.1.0'
      }
    }
  ],
  warn: [
    {
      'a-dependency-with-an-issue': {
        versionSpecified: '~1.0.0',
        versionInstalled: '1.1.0',
        warning: 'Installed version is too far ahead of specified version'
      }
    }
  ]
}
  • Ok: Array of dependency names that are installed, and whose installed version satisfies the requirements of package.json (or package-lock.json if present)
  • Missing: Array of dependency names that were not found on the filesystem
  • Outdated: Array of dependency names that are outdated, and thus do not satisfy the requirements of package.json (or package-lock.json if present)
  • Warn: Array of dependency names that have an issue (e.g. non-conformance to semver; specify a tag, but cannot be found in package-lock.json, etc.)

Caveats

  • depStatus only checks the installed status of dependencies, and does not check devDependencies