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

but

v2.0.1

Published

If only there was a way to pass along a callback with just a single argument.

Downloads

176

Readme

but

But expands your functional horizons to the edge of the universe

If only there was a way to pass along a callback with just a single argument.

You know how you like chaining asynchronous function calls but sometimes weird arguments get in the way of your waterfall series with unpredictable arguments?

How about attempting to parseInt in a map only to find out map spews three arguments?

NO MORE!

npm install but --save

Usage

Functional arguments giving you headaches?

Before
n.map(function (val) {
  return parseInt(val);
});
After
n.map(but(parseInt));

Works on .forEach or any functional array method as well! Classy.

Before
n.forEach(function (val) {
  console.log(val);
});
After
n.forEach(but(console.log));

Mongoose being weird?

Before
async.waterfall([
  function (next) {
    new User(model).save(function (err) {
      next(err);
    });
  },
  function (next) {
    // MOAR CODE
  }
])
After
async.waterfall([
  function (next) {
    new User(model).save(but(next));
  },
  function (next) {
    // MOAR CODE
  }
])

Why?

It had to be done. It is known.

License

MIT