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

@sesamecare-oss/check-package-changes

v1.1.1

Published

Compare a published package against local files

Downloads

100

Readme

check-package-changes

This package compares a set of local files with the current published NPM version of a target package. This can be useful for things like generated modules (think OpenAPI specifications) where you would like to know if the generated code matches the currently published code or not.

For example:

npx @sesamecare-oss/check-package-changes my-package-name --verbose --ignore-version --local-dir generated "dist/**" package.json spec.json
  • --verbose will print out the name of any file that is not the same between the sources
  • --ignore-version will ignore the version value in package.json (assuming package.json was specified) which can be useful when your package version is not yet known locally.
  • --local-dir points to the directory containing the files (cwd is used otherwise)
  • "dist/**" package.json spec.json - these are the files (or glob patterns) that are examined in both sources.