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

easy-sync

v1.0.0

Published

A simple yet flexible synchronization utility.

Downloads

6

Readme

Easy Sync for Node.JS

A simple yet flexible synchronization utility.

What's it do?

Allows you to easily run parallel and sequential actions, however you want to run them.

Why's it needed?

It may not be. But if you need to do what this does, then you may need it. If you are running some asynchronous processes which need to "wait" for other asynchronous processes to complete, this will help you accomplish such a feat.

How's it work?

You define a timeline and a callback and send them to sync which will run your timeline as you've described it and then execute the callback when the timeline has been completed.

How do I use it?

It's very straightforward.

void sync([timeline, callback, errorCallback]);

Parameters timeline (optional) is either a function or an array. If it's an array, the elements of that array can be function or other arrays. This allows you to create complex timelines with nested actions.

callback (optional) is a function which is executed when the timeline has been completed, its signature is as follows:

void callback()

errorCallback is a function which is executed if an error occurs, its signature is as follows:

void errorCallback(message)

Notes

  • timeline is optional, in case you're building a timeline dynamically and in some cases it could be empty.
  • Note that either callback or errorCallback are executed, never both.

Where are the examples?

You can view the tests in test/test.js, or see below.

Simple Example

Run action1 and action2 (which are async functions) in sequence, the callback is executed once both have completed.

sync([action1, action2], callback);

Run nested actions (in order) to create visually descriptive timelines.

sync([
    action1,
    action2,
        [action3, action4, action5], // Actions 3, 4, and 5 are conceptually similar.
    action6],
    callback);

Run some actions in sequence and some in parallel. This example will run in sequence from top to bottom, but the parallel2_1 and parallel2_2 actions will run at the same time as each other. Once they complete, sequence3 will run, and then finally the callback will run.

sync([
    sequence1,
    [
        sequence2,
        sync.p([
            parallel2_1,
            parallel2_2]),
    sequence3],
    callback);