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

canicas

v0.0.2

Published

Keep track of your callbacks even without promises

Downloads

3

Readme

Canicas

ca-ni-cuz

Sometimes promises are too much. Example:

var knex = require('knex')({client: 'pg', connection: process.env.PG_CONNECTION_STRING});

for (var i = 0; i < 5; i++)
{
  knex('products').insert({title: i + ' bananas', description: 'Full of potassium!'}).then(function() {
    // Don't care
  });
}
// Need to teardown knex pg connection somehow after all inserts are done / callbacks are called

In that case add the function you want to be run when all of your callbacks have fired:

var canicas = require('canicas');
canicas.done = function() {
  knex.destroy(function() {});
};

Add one every time you spin out a new async function:

// snip
for (var i = 0; i < 5; i++)
{
  canicas.inc();
  knex('products').insert({title: i + ' bananas', description: 'Full of potassium!'}).then(function() {
//snip

And make sure to register when a callback has finished:

// snip
knex('products').insert({title: i + ' bananas', description: 'Full of potassium!'}).then(function() {
  // Some important code

  canicas.dec();
};

When all callbacks have been fired the function you registered with canicas.done will be called.

NOTE: done WILL be called as soon as the canicas internal counter reaches 0. If you have 5 callbacks, you spin one out, and it completes before you've incremented the counter done will be called and it could mess up your other 4 callbacks. I'll fix that in the next version.