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

promise-node

v1.0.4

Published

A simple way to handle asynchronous.

Downloads

4

Readme

promise-node

A simple way to handle asynchronous.

install

$ yarn add promise-node

or

$ npm install --save promise-node

usage

Use .start(param1, param2, ...) to pass arguments to the first promiseNode's function.

Use .next(param1, param2, ...) to pass arguments to next promiseNode's function.

When you using function () {}, you can use this.next() or instance.next() to resolve this function, but when you using arrow function, instance.next() is the only way to resolve this arrow function.

class mode

import PromiseNode from 'promise-node'

const p1 = new PromiseNode(function (a) {
  console.log('start')
  setTimeout(() => {
    console.log(a++)
    this.next(a, 'hah')
  }, 2000)
})
const p2 = new PromiseNode((b, str) => {
  console.log(b, str)
  p2.next(b + str)
})
const p3 = new PromiseNode((c) => {
  setTimeout(() => {
    console.log(c)
    console.log('end')
  }, 1000)
})

p1.setNext(p2).setNext(p3)
p1.start(0)

fn mode

When you open this mode, the Function.prototype will add two function.

import PromiseNode from 'promise-node'

PromiseNode.fn() // open `fn` mode

const p1 = function (a) {
  console.log('start')
  setTimeout(() => {
    console.log(a++)
    p1.next(a, 'hah')
  }, 2000)
}
const p2 = (b, str) => {
  console.log(b, str)
  p2.next(b + str)
}
const p3 = (c) => {
  setTimeout(() => {
    console.log(c)
    console.log('end')
  }, 1000)
}

p1.setNext(p2).setNext(p3)
p1(0)

I made this repo just for fun and learn CoR pattern.

There are lots of better way to handle asynchronous, you even can change Koa's onion model (or other framework) to handle asynchronous, I'm just a FE beginner and very interested in it.