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

asynchron

v1.0.21

Published

Small library that adds wait, async pattern to promises. Internally it adapts Q promises but have very diffrent API outside. Created mainly for simplifying code within Swarm projects

Downloads

4

Readme

Very small library that add the wait, async pattern to promises in Java Script (currently we are using Q library).

Asincrons p[rovides syntactic sugar on promises APIs to clean the code but it is also very important for swarm project (especially for SwarmCore)
It is mandatory to use asynchron module when working with swarm phases.

By using swait, the swarm runtime can track execution contexts to handle security, multi-tenancy, handle errors properly,etc. of coyrse, asynchron can be also used outside of swarm projects.

Installation:

npm install asynchron

Example 1: reading the content of a file

    var myFileContent = fs.readFile.async("fileName.txt");
    (function(content){
        console.log(content);
    }).wait(myFileContent);

    //myFileContent is a Q promise and you can do other Q things with that promise

Example 2:

For example, we have 2 functions (asynchronous APIs for dealing with penguins), using node.js return convention

    loadPenguin(nickName, callBack)
    loadPenguinFamily(father, mother, callBack)

now, let's see how we load some Penguins

    var father = loadPenguin.async('MrPenguin');
    var mother = loadPenguin.async('MrsPenguin');
    var family = loadPenguinFamily.async(father, mother);

    (function (family){
        console.log(family); //whatever
    }).wait(family);

Simple functions (all added in Function.prototype for better syntax):

wait()

functionReference.wait(...)

calls functionReference when all promises are fulfilled. They become parameters for callback call.

swait()

functionReference.swait(...)

same with wait but has an additional call to preserve swarm phase environments. This functions should be used only with SwarmUtil, SwarmESB or SwarmCore derived projects.

async()

functionReference.async(...)

Make an asynchronous call when possible , returns a promise that get fulfilled when all the arguments are fulfilled.

nasync()

similar with async but ignores errors, fulfills the promise with a null value... the programmer should test for null values (errors are normal part of the logic in many cases (missing a key in cache, etc))

error handling

wait, swait primitives can take a function as the last argument. On errors happening in any asynchronous call, that function will be called once. The fail approach documented bellow is now marked obsolete as it is usually much easier to just pass a callback (eventually chain an inherited one) than to create a fail block

#OBSOLETE functions, do not use, il will be removed in the next versions

fail()

functionReference.fail(...)

call the functionReference when a promise given as argument has failed. The callback will be called with an Error.

timeout(timeout, )

functionReference.timeout(...)

like fail, but also get called if any promise given as arguments is unfulfilled until timeout expires. The callback will be called with an Error. Do not use both fail and and timeout, they will be both called!