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

sanitycheck

v2.0.2

Published

ensure that all deps are present and accounted for CI / CD

Downloads

163

Readme

sanitycheck

ensure that all deps are present and accounted for CI / CD

js-standard-style

usage

add it as a dev dependency to your project

$ npm install --save-dev sanitycheck

and add it to your test command by editing your package.json:

{
  "scripts": {
    "test": "sanitycheck && <test runner>"
  }
}

Now you can run it using $ npm test and add it to your favorite testing or CI scripts.

If there are any errors, it exits with an error code of 1. As of 2.0.0, dependencies found in package.json but not used in code count as errors.

example output:

ok

Checking for unused or missing dependencies in package.json...
Validating all require statements...
···
OK

missing dependencies

Checking for unused or missing dependencies in package.json...
Dependencies missing in package.json: cool-ascii-faces

depenency case error

Checking for unused or missing dependencies in package.json...
Validating all require statements...
·☹ ·
1 Errors:
Error: Inside "c:\dev\sanitycheck\index.js"
Cannot resolve "./SUB" because:
"c:\dev\sanitycheck\SUB.js" doesn't exactly match the actual file path
"c:\dev\sanitycheck\sub.js"

kudos

makes use of excellent work from @thlorenz in valiquire and @jutaz in depscan

contributors

license

ISC. (c) MMXIV jden [email protected]. See LICENSE.md