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

check-david

v0.0.4

Published

No-nonsense dependency checks for your package.json

Downloads

5

Readme

check-david

npm Codeship Dependency Status devDependency Status node License

No-nonsense dependency checks for your package.json

A simple command line tool that checks whether your dependencies are up to date (using David) and outputs a checkstyle-compatible XML report.

Use Case

This module attempts to solve a very specific problem and thus has the following semantics:

  • if you're at least one patch versions behind, an informational message will be generated
  • if you're at least one minor versions behind, a warning will be generated
  • if you're at least one major versions behind, an error will be generated

If you set the --force-pinned (and/or --force-dev-pinned) flag, unpinned dependencies will cause an error. If needed, you can completely ignoring packages. If you have a specific feature request, feel free to create an issue.

Usage

$ npm i -g check-david
$ check-david /absolute/path/to/package.json > check-david.xml

# or execute the script from your module directory:
$ cd projects/awesome-stuff
$ check-david > check-david.xml  # uses the package.json in the current directory

Unless an internal error occurred, check-david will always terminate with an exit code of zero. Use the mechanisms provided by your build system to fail if needed.

You can ignore patch and minor version updates by using the --level minor or --level major command line option, respectively. Not that this does not affect the severity of the generated messages.