Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Javascript concurrency and order-preserving channels. You can consider this a streaming async.parallel
with concurrency control that returns results in the correct order. Or a transform stream that executes multiple "transforms" at once.
This is very similar to other libraries like batch and co-queue except:
Infinity
by default)The general use-case is concatenating files (as the example above).
var chanel = require('chanel')
co(function* () {
var ch = chanel()
// only two file descriptors open at a time
ch.concurrency = 2
var files = [
'1.txt',
'2.txt',
'3.txt',
'4.txt',
'5.txt',
'6.txt',
]
// create and push the functions or "tasks"
files.forEach(function (filename) {
ch.push(function (done) {
fs.readFile(filename, 'utf8', done)
})
})
while (ch.readable) {
// write each file to stdout in order
process.stdout.write(yield ch)
}
// exit the process (unnecessary)
process.exit()
})()
or concatenate them all with:
var results = yield ch(true)
var string = results.join('')
For this specific example, you're better off using combine-streams, but there are use-cases where you need to buffer the entire file such as build systems with compilation steps.
concurrency
- maximum number of concurrent callbacksdiscard
- discard the results of the callbacks. Will only throw errors, if any, if true
.closed
or open
- by default, the channel is closed, meaning yield ch(true)
will flush only the remaining callbacks. If opened, yield ch(true)
will not yield until the channel is closed.Push a thunk to the channel. If the thunk returns multiple arguments, it will be sliced into an array (just like co).
Pull the next value in the channel. This waits for the next result in the channel indefinitely whether or not the channel is closed.
If an error was thrown, this function will return that error, and no more additional callbacks will be executed. To continue executing callbacks, just yield ch
again.
If ch.discard === false
, errors will be returned in the correct order. Otherwise, errors will be returned ASAP.
Note that this is a function. If you are not using generators, you can do something recursive like:
ch(function next(err, res) {
if (err) throw err;
if (res) console.log(res);
if (ch.readable) ch(next);
process.exit();
});
When using co
generators, you can just yield
it.
co(function* () {
while (ch.readable) console.log(yield ch);
})
Waits until all the pending callbacks are completed. I personally call this "flushing the channel". Unless you are discarding data, all the results of the callbacks will be returned as the array results
.
This is essentially the "give me everything method". Without generators, you can do:
ch(true, function (err, results) {
})
Number of results waiting to be read.
A boolean to check whether you can yield* ch.read()
. Otherwise, a yield* ch.read()
call may never be yielded.
Whether the channel is closed. true
by default.
Opens the channel. When the channel is opened, yield ch(true)
will not yield
until the channel is closed.
Closes the channel.
If the channel is closed, yield
s immediately.
If the channel is opened, returns true
if data has been pushed and returns false
if the channel has been closed, which means there is no data to read.
If you're using an open channel, you want to wait until yield ch.pushed
before you start reading the data.
FAQs
Channel-based control-flow for parallel tasks with concurrency control
The npm package chanel receives a total of 2,388 weekly downloads. As such, chanel popularity was classified as popular.
We found that chanel demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers 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.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.