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

provenance

v1.0.1

Published

A CLI script that takes a position in a JS file inside an npm package, and outputs a directed graph of all of the functions that call the function at that position.

Downloads

31

Readme

provenance

A CLI script that takes a position in a JS file inside an npm package, and outputs a directed graph of all of the functions that call the function at that position.

demo

installation, or:

vim + graphviz + quicklook

My provenance setup requires:

  • iojs v2.x
  • graphviz (via homebrew)

I wrote this so I could mash <Leader>sx and get a quick heads up display of what calls the function I'm looking at. To that end, I wrote a script to store stdin as a tempfile and use qlmanage to quickly display it:

#!/bin/bash
# call this file "ql" and `chmod +x` it
tmpfile=$(mktemp -t ql)
mv "$tmpfile"{,.png}
tmpfile=${tmpfile}.png
cat > "$tmpfile"
qlmanage -p $tmpfile >& /dev/null
rm $tmpfile

With that file on $PATH as ql, I added the following info to my .vimrc:

" ~/.vimrc
nmap <leader>sx :exe "!iojs /path/to/provenance/bin/provenance % " . line(".") . " " . col(".") . "\| dot -Tpng \| ql" <CR>

notes

Provenance trys to note all calling paths into your current function.

  • It attempts to note "inversion of control" (or ioc) calls, though it sometimes misses.
  • It will definitely miss call that is a result of a dynamic lookup: obj[something]().
  • It needs a valid package.json at the root of your project to build a list of files to look at. If your file is not indirectly required by the "main" script of your package.json, it may not produce useful output.
  • It will also note "defs" relations — as in, "this function is defined by another function."
  • It only notes any given function once at most — there may be many paths through a function to your current function, but it will only appear once.

license

MIT