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

promisify-global

v1.0.0

Published

adds .promise to Function.prototype so you can always turn callback-based functions into promise-based functions.

Downloads

5

Readme

Adds .promise() to 🚨Function.prototype🚨

npm install promisify-global

If you would normally call some_function(function(e, val){...}), instead you can get a promise by using some_function.promise().

Example: is_doge

require('promisify-global');

// is_doge normally uses callbacks
function is_doge(arg, cb) {
  if (arg !== 'doge') {
    cb(arg + ' not doge')
  } else {
    cb(null, 'wow such doge')
  }
}

// but hey it's so easy to get a promise for it
var doge_promise = is_doge.promise('doge');

doge_promise.then(function(val) {
  console.log('wof!')
})

IT'S JUST THAT SIMPLE.

there could be no negative fallout from adding .promise to Function.prototype. like if it does somehow mess up everything, that probably means you've got 99 problems already, and trying to use this library won't really help solve those problems.

yep.

...

...

...

adding to Function.prototype is not bad at all.

...

...

...

...

...

...

...

...

...

...

...

...

Flowey