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-version-upgraded

v1.0.8

Published

Checks that a package has been updated compared to a remote registry.

Downloads

23

Readme

Overview

A lightweight utility that checks whether or not a local package.json file has a higher version number than what is published to a package registry. This will prevent publishing failures that may happen later in your CI/CD pipelines.

Run

Install

npm install -g check-version-upgraded

Run

CLI

Parameters

  • package.json file path
  • Optional registry to check. The default is npmjs

Example

npx check-version-upgraded ./my-module/package.json https://registry.npmjs.org

Output

The tool will print a simple true is printed to the console standard out if the local package.json version number is greater than what is published to the registry. If the local version is less than or equal to the published version, a false is printed to the standard error stream.

Programmatic

Example

import { checkVersionUpgraded } from "check-version-upgraded";
(async () => {
  const upgraded = await checkVersionUpgraded("./package.json");
  console.log(upgraded);
})();

Output

The checkVersionUpgraded returns a Promise<boolean> indicating if the local package is upgraded.

Develop

Install Dev Dependencies

npm install

Compile

npm run build

Watch

npm run watch

Wishlist

  • Add custom result handlers instead of always returning a simple boolean or printing to the console
  • Add unit tests
  • Use awaits instead of promise chains