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

multi-tasks

v2.0.5

Published

multi-tasks

Downloads

13

Readme

multi-tasks

multi-tasks

Install:

npm install multi-tasks

How to use:

//see examples/example0
let multiTasks = require('multi-tasks').multiTasks;


//Step1, If you have tasks that need to be executed simultaneously, please provide them as an array, multi-tasks will automatically split them and execute.
let alltasks = [];
for(let i=0;i<50;i++){
    alltasks.push({
        name: `task-${i}`,
        data: `This prop is for a subtask`
    });
};

//Step2, Provide a function to process a certain sub-task and return the result data
let processTask = (task, helper)=>{
    let {taskCount} = task;

    return 'a result which is not a promise'; 
};

//Step3, run!
multiTasks({
    initialTasks: alltasks, 
    processTask, 
    taskRootFolder: `../examples-tmp-data/example0`, //a directory to store progress and results files, you can check the progress here
    taskId: 'my-task',
    numberOfWorkers: 3, //Assign how many workers are working in parallel
    //autoCloseAfterCompletion: true, //if you have dynamically generated new tasks, put this as false
    shouldTerminate:(info)=>{
        //return true if you need to terminate the whole process
    },
    onFinish: (report)=>{
        console.log('finish callback', report);
    }
});

Have a try:

node examples/example0/run
node examples/example1/run

More about the task processing function

//you can return a promise for async processes
let processTask = (task, helper)=>{
    let {taskCount} = task;

    return new Promise((resolve, reject)=>{
        resolve({
            data:`task${taskCount} complete`
        })
    })
};

//dynamically create a new task while processing
let processTask = (task, helper)=>{
    let {taskCount} = task;

    
    if(taskCount % 2 === 0){
        helper.createNewTasks({//You can dynamically create a new task if find something new while processing
            msg:'a new task'
        });
        return;
    }

    return new Promise((resolve, reject)=>{
        resolve({
            data:`task${taskCount} complete`
        })
    })
};

//this example shows how to generate/handle exceptions
let processTask = (task, helper)=>{
    let {taskCount} = task;

    //This is the demo of exceptions/errors, they will be captured and saved in the results/errors folder
    if(taskCount===3) throw 'exception';
    if(taskCount===4) return Promise.reject({err:'a test error'});
    if(taskCount===5) aaa =  bbb;

    if(taskCount===6) return 'a result which is not a promise'; //Return a non-promise result is OK

    //by default, you should return a promise, all returned data can be found in the results/succ folder
    //but to return a non-promise result is also OK, see above
    return new Promise((resolve, reject)=>{
        setTimeout(()=>{
            if(taskCount % 2 === 0){
                helper.createNewTasks({//You can dynamically create a new task if find something new while processing
                    msg:'a new task'
                });
                resolve()
            }else{
                resolve({
                    data:`task${taskCount} complete`
                })
            }
        }, 10)
    })
}

Changelog:

  • 2.0.5 Update readme examples
  • 2.0.4 Support resume from a failed task
  • 2.0.3 Fix: mkdir bug on windows
  • 2.0.2 new feature: support shouldTerminate
  • 2.0.1 Avoid possible I/O conflicts.
  • 2.0.0 Rewritten with a new architecture to support dynamic tasks.
  • 1.2.8 Fix: create task folder failed on MacOS
  • 1.2.7 Small updates
  • 1.2.6 Support onFinish event
  • 1.2.5 Rename numberOfWorks to numberOfWorkers, the old one are still supported ;-)
  • 1.2.4 Fix: opt.numberOfWorkers not work
  • 1.2.3 Update README
  • 1.2.2 Update README and examples
  • 1.2.1 Handle exceptions and errors in subtasks
  • 1.2.0 Simplified usage by providing the function way and support return Promise
  • 1.1.4 Remove make-dir
  • 1.1.3 Simplified usage, see example0
  • 1.1.2
  • 1.1.1 Rename files, updated changelog
  • 1.1.0 Simplified the usage of a customized Consumer, see example0
  • 1.0.8 Fix examples
  • 1.0.7 Remove moment
  • 1.0.6 Performance optimization

Github:

https://github.com/zhanglei923/multi-tasks