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

supersniff

v2.1.0

Published

A simple function for debugging stuff like promise chains and other pipeline-like thingees. It just creates a function that console logs whatever is passed to it and then returns that value.

Downloads

171

Readme

supersniff

A simple function for debugging stuff like promise chains, streams and other pipeline-like thingees. It just creates a function that console logs whatever is passed to it and then returns that value

Example:

const sniff = require('supersniff')

fetch(`http://myapi.com/users/${username}.json`))
  .then(response => response.json())
  .then(sniff) // Will console.log out the parsed json, and return the value,
               // effectively passing it on to the next .then
  .then(user => Promise.all(user.friends.map(friend => getFriend(friendId))))
  .then(friends => /* do even more stuff here */)

Why this is useful?

Lets say that you have a promise chain that looks like this ...

getData()
  .then(transformData)
  .then(sortData)

... and you are debugging an issue that makes you want to inspect what the data looks like after the transformData operation, but BEFORE the sortData operation. No matter if you want to do this by breakpoint or console.log, you need to wrap transformData in a multiline functions:

getData()
  .then(x => {
    console.log(x) // alternatively, breakpoint on the line below
    return transformData(x)
  })
  .then(sortData)

It's not a huge hassle, but I found myself doing it a LOT, and with supersniff there is a lot less typing:

getData()
  .then(transformData)
  .then(sniff)
  .then(sortData)

Yes, this is stupidly simple, but I've found myself writing this function 40000 times now so I want it on npm, OK? OK!?????

Overrriding prefix

supersnitt will log to console with a [SNIFF] prefix but if you want to override it like this:

const sniff = require('supersniff')

fetch(`http://myapi.com/users/${username}.json`))
  .then(response => response.json())
  .then(sniff.tag('MYTAG'))