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

package-versions

v0.1.0

Published

Helps auto-update node projects as npm dependencies change

Downloads

18

Readme

package-versions

You have better things to do than figuring out when to run npm install in your node app.

Whether it's a first install, or someone just pushed a new or changed dependency to package.json underfoot.

Here – use this Makefile stub:

# add a `.package-versions` dependency to all node targets
dev: .package-versions
	npm start # or however you invoke your app

# Bootstrap the app for development, auto-installing node_modules if not present
node_modules/*/package.json:
setup:
	@npm install

# Auto-upgrade node_modules; runs for any make target that uses node, as soon as
# package.json names a package or version not already installed. To bypass this,
# (if you are testing with some older version), "touch .package-versions" before
# you run "make <something>", so this automated dependency does not kick in.
.package-versions: package.json node_modules/*/package.json
#	0 = up to date | 1 = need to update | 2 = abort; failed dependency urls
	@echo 'installed package versions:'
	@node $(BIN)/package-versions -- --dump > $@ ; case $$? in \
	  0) cat $@ ;; \
	  1) rm $@ \
	   ; echo '*** Running \x1B[32mmake setup\x1B[39m for you ***' \
	   ; make setup ;; \
          127) rm $@ ; echo '*** Please install node! ***' ; false ;; \
	  *) false ;; \
	esac