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

@msimerson/dependency-version-checker

v1.1.2

Published

Check for newer versions of dependencies.

Downloads

3

Readme

Dependency Version Checker

This library allows you to run a check for newer versions against your development and production dependencies, both npm and git:///git+ssh://.

Motivation

Internal libraries or other dependencies should be as easy to verify as those published to npm. And you should have one tool for that.

Prerequisites

For git, if you're able to clone the repo, you're able to check the tags.

For npm, there's no support for custom, manual repositories. If you're using custom repository, make it work without any additional parameters.

Configure your npm, git and ssh if you have private repos.

Disclaimer

This is "for dev by dev" tool. They may be some assumptions made, so do not hesitate to look into verbose logs if something seems not right.

Still, I'll try to list all assumptions in this file.

  • Tags are in semver, if they do not pass semver parsing they do not show in the list.

Installation

npm install -g dependency-version-checker

Usage

Run in your project (you do not need to be exactly in root):

dep-versions --help
dep-versions check [rule] //checks dependencies and prints them in table
dep-versions update [rule] //checks dependencies and update them in found package.json

Rule parameter

  • Rule parameter is a string by which successful match against the dependencies.
  • Rule parameter may be omitted, but check will be executed against all the dependencies.

Example

$dep-versions check lod
Performing dependency updates check for project: D:\Documents\Projects\depdency-version-checker\spec\package.json.
Check will be performed for dependencies matching this regex: /lod/.

You could update 1 dependency(/-ies).

Dependency  Type  Current Version  Latest Minor  Latest Major  
==========  ====  ===============  ============  ============  
lodash      Prod  3.0.0            3.10.1        4.17.11     

Debugging

Run dep-versions <command> --help to see additional flags.