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 🙏

© 2025 – Pkg Stats / Ryan Hefner

patch-pulse

v2.9.0

Published

Check for outdated npm dependencies

Readme

Patch Pulse CLI

Check for outdated npm dependencies in your package.json file.

License npm Version npm Downloads CI/CD GitHub stars

Patch Pulse Banner

Quick Start

npx patch-pulse

That's it! Patch Pulse scans your package.json and shows which dependencies are outdated.

Example Screenshot

Configuration

Patch Pulse supports configuration files for persistent settings. Create one of these files in your project root:

  • patchpulse.config.json
  • .patchpulserc.json
  • .patchpulserc

Configuration File Example

{
  "skip": ["lodash", "@types/*", "test-*"],
  "packageManager": "npm",
  "noUpdatePrompt": false
}

Skip Patterns

The skip array supports multiple pattern types:

  • Exact names: "lodash", "chalk"
  • Glob patterns: "@types/*", "test-*", "*-dev"
  • Regex patterns: ".*-dev", "^@angular/.*", "zone\\.js"

Package Manager

The packageManager option allows you to override the package manager detection.

  • npm
  • pnpm
  • yarn
  • bun

No Update Prompt

The noUpdatePrompt option allows you to skip the update prompt.

CLI vs File Configuration

CLI arguments override file configuration:

# This will override any settings in patchpulse.config.json
npx patch-pulse --skip "react,react-dom" --package-manager pnpm --no-update-prompt

Ecosystem

Troubleshooting

  • "No dependencies found" - Run from directory with package.json
  • "Error reading package.json" - Check JSON syntax and file permissions
  • Network errors - Verify internet connection and npm registry access

Contributing

  1. Fork and clone
  2. npm install
  3. Make changes
  4. Submit PR

Guidelines: Add tests, update docs, keep commits atomic.

Support

License

MIT - see LICENSE

Author

@BarryMichaelDoyle

🎥 Live Development: Sometimes I stream on Twitch - drop by and say hello!


Made with ❤️ for the Node.js community