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-published

v0.0.1

Published

Determine when modules in your project were updated

Downloads

3

Readme

npm-published


Determine when node modules in your project have been updated

still developing

CLI

node bin/npm-published.js --source </path/to/package.json> --from <published> --days

options

--source, -s : source path to package.json
--from, -f   : filter packages published before date. optional, defaults to epoch
--to, -t     : filter packages published after date. optional, defaults to now
--deps, -d   : show prod, dev, or both dependencies. defaults to both,
               valid options are prod, dev, all
--days       : show how many days ago from today the package was published

API

.query(source, [from=epoch], [to=now], [options])

Query the NPM registry for publish timespamps

Parameters

  • source {String} - path to the package.json file to examine
  • [from=epoch] {String | Date} - modules published before this date are filtered out
  • [to=now] {String | Date} - modules published after this date are filtered out
  • [options] Object - hash of options
    • deps {String} - dependencies to examine, valid values are prod, dev, and all
    • showDays {Boolean} - show the published date as days ago from today

Returns {Promise} - Resolves results object

.log

Settable property for custom logging function

Example

var published = require('npm-published')

// custom log function
published.log = function (obj) {
    if (obj.level === 'error') console.log('ERROR:', obj.time, obj.message)
}

// npm query
published.query('/projects/example/package.json', '2016-01-01', undefined, {
    deps: 'prod',
    showDays: true
}).then(function (results) {
    // do something with results
})

TODO:

  • add recursive dependency support to determine what dependencies have been updated
  • add node_modules support to determine what currently installed node_modules have recently changed
  • add more output options
  • add input options for days ago i.e. -from 2daysago