
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
@pscraper/taskm
Advanced tools
This lib is for a managing a large number of tasks, by adding each task into queue, and digesting each of them one by one. These are the the resaon why using `taskm`: - you got a large number of task to handle, an execption may cause the script to restar
This lib is for a managing a large number of tasks, by adding each task into queue, and digesting each of them one by one. These are the the resaon why using taskm:
pending, finished and fail(sqlite is used to manage queue)
$ yarn add @pscraper/taskm
or
$ npm install @pscraper/taskm
More Example: https://github.com/wahengchang/pscraper/tree/master/packages/demo/taskm
adding new task to queue (FIFO)

const TM = require('@pscraper/taskm')
const taskm = new TM()
await taskm.init()
const uniqueId = "amazingId"
const options = {
title: 'amazingTitle',
meta: JSON.stringify({key: "key1"})
}
await taskm.add(uniqueId, options)
consumming task from queue
const TM = require('@pscraper/taskm')
const taskm = new TM()
await taskm.init()
const item = await taskm.getFirst()
// do something
await taskm.markFinished(item.id)

adding new task to queue
const TM = require('@pscraper/taskm')
const taskm = new TM()
await taskm.init()
for(let i =0 ; i<999999; i++) {
const id = `mockId${new Date().getTime()}-${i}`
const title = `${id}-title-${i}`
inputList.push({id, title})
await taskm.add(id, {title})
}
consumming task from queue, usually is run on more than one PC parallelly
const TM = require('@pscraper/taskm')
const taskm = new TM()
await taskm.init()
const item = await taskm.getFirstRandom()
// do something
await taskm.markFinished(item.id)
| Function | Description |
|---|---|
init() | init DB connection |
purge() | remove all existed ada |
add(uniqueId = '', body = {}) | adding a new task to queue |
getFirst(condition={}) | getting one task from queue, default FIFO |
getFirstRandom(condition={}) | getting one task from queue randomly |
getTaskById(id) | getting one task by given id |
listAllTasks(condition={}) | return all created and fail tasks |
markFinished(id) | mark task as finished, would appear in getFirst() |
markFail(id) | mark task as fail, would appear in getFirst() |
FAQs
This lib is for a managing a large number of tasks, by adding each task into queue, and digesting each of them one by one. These are the the resaon why using `taskm`: - you got a large number of task to handle, an execption may cause the script to restar
The npm package @pscraper/taskm receives a total of 0 weekly downloads. As such, @pscraper/taskm popularity was classified as not popular.
We found that @pscraper/taskm demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.