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

npm-dependency-versions

v0.3.0

Published

A utility for determining the package versions at given points in time

Downloads

33

Readme

depver

Install

npm i -g npm-dependency-versions

Binary dependencies

You'll need node & npm. Detective mode also requires git to be on the path.

CLI

Usage: depver [packages...]

Determine the latest available version of npm packages at a given point in time. Parses local package.json if no packages are specified. Git blames local package.json to infer dates if no dates are specified either.

| Options: | | |---|---| | -h, --help | output usage information | | -d, --date [date] | the date at which the packages should be versioned (defaults to the present moment) | | -o, --output [filename] | file to write the output to (defaults to stdout) |

Examples

depver

Assumes you are in the root of an npm package (which does not need to be published on npmjs.org), which is git versioned. Git blames package.json in the current folder, determines when each dependency entry was added, and queries npmjs.org to determine which specific version of each dependency would have been returned at that time given the version range specified.

depver --date=2016-07-06

Assumes you are in the root of an npm package. Determines what versions of each dependency in the local package.json would have satisfied the specified version range therein on 2016-07-06.

depver mithril urijs --date=2016-07-06

Determines what the latest versions of mithril and urijs would have been on 2016-07-06.