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 🙏

© 2026 – Pkg Stats / Ryan Hefner

for-next

v1.0.3

Published

simple for loop iterator thing

Readme

for-next

simple for loop iterator thing

Simple example


const $for = require("for-next");

$for(["cat", "dog", "dingo"], (animal, {next}) => {

  console.log("animal: ", animal);
  // The iterator won't continue if you don't invoke next().
  // the object specified can have a value property
  // which the iterator collects all values to output when resolved.
  next({value: {isCat: animal === "cat"}})

// The interval is the amount of time in milliseconds
// to wait per iteration. If you set this to 0 (or don't specify),
// the iterator won't use setTimeout (so be careful of stackoverflows)
}, {interval: 500})
  .then(values => {

    const cats = values.filter(animal => animal.isCat);
    console.log("Cats: ", cats.length);

  })
;

More examples


const countdown = 5;
$for(countdown, (index, {index, next, stop, values, ctx}) => {

  let count = countdown - index + 1;

  if(count <= 3){
    if(ctx.counted){
      count -= .5;
      next({value: count});
    }else{
      // You can skip forward/backward
      next({skip: -1, value: count});
      // The ctx variable is the context scoped to individual iterations (AND skipped iterations).
      // For example, if you skip to another iteration, it will pull the current context with it.
      ctx.counted =  true;
    }
  }else{
    next({value: count});
  }

  console.log(count);

}, {interval: 1000})
  .then(values => {
    console.log("Go!");
    console.log({values});
  })
;
/* OUTPUT */
// 5
// 4
// 3
// 2.5
// 2
// 1.5
// 1
// Go!
// { values: [ 5, 4, 3, 2.5, 2, 1.5, 1 ] }

More examples work in progress..