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

flat-flow

v1.3.0

Published

Async flow with conditional branching that looks good.

Downloads

29

Readme

Summary

Tiny flow with conditional branching.

Installation

npm install flat-flow --save

Usage

{ flow } = require 'flat-flow'

# This is how to use me.
flow [

  # 1-arity functions are called and result from (err, result) merged with locals.
  # If you pass an error as first arg, the whole flow will be finished, see the bottom.
  (done) ->
    done null, { a: 1, b: 2 }

  # 0-arity functions that return boolean manage the flow; false will all calls until true is found in 0-arity.
  -> false

  # Will be skipped.
  (done) ->
    done null, { c: 3 }

  # Resume flow. You have access to locals merged before.
  -> @a is 1

  # Will be called because we resumed the flow above.
  (done) ->
    done null, { e: @a + @b }

  # 2-arity functions allows you to refer to locals if you don't want to bind all nested functions.
  (done, { e }) ->
    process.nextTick ->
      process.nextTick ->
        done null, { f: e + 1 }

  # ...otherwise you can use locals directly
  (done) ->
    process.nextTick => # fat
      process.nextTick => # fat
        done null, { g: @f + 1 }

], (err, { e, f }) -> # final callback, always called.
  assert.ifError err

  # Locals are here as well.
  assert.equal @a, 1
  assert.equal @b, 2
  assert.equal @c, undefined
  assert.equal @d, undefined

  # Or you can access them from optional 2nd argument.
  assert.equal e, 3
  assert.equal f, 4

  assert.equal @g, 5