Security News
RubyGems.org Adds New Maintainer Role
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Chainable asynchronous flow control with sequential and parallel primitives and pipeline-style error handling
Seq is an asynchronous flow control library with a chainable interface for sequential and parallel actions. Even the error handling is chainable.
Each action in the chain operates on a stack of values. There is also a variables hash for storing values by name.
var fs = require('fs');
var Hash = require('traverse/hash');
var Seq = require('seq');
Seq()
.seq(function () {
fs.readdir(__dirname, this);
})
.flatten()
.parEach(function (file) {
fs.stat(__dirname + '/' + file, this.into(file));
})
.seq(function () {
var sizes = Hash.map(this.vars, function (s) { return s.size })
console.dir(sizes);
})
;
Output:
{ 'stat_all.js': 404, 'parseq.js': 464 }
var fs = require('fs');
var exec = require('child_process').exec;
var Seq = require('seq');
Seq()
.seq(function () {
exec('whoami', this)
})
.par(function (who) {
exec('groups ' + who, this);
})
.par(function (who) {
fs.readFile(__filename, 'ascii', this);
})
.seq(function (groups, src) {
console.log('Groups: ' + groups.trim());
console.log('This file has ' + src.length + ' bytes');
})
;
Output:
Groups: substack : substack dialout cdrom floppy audio src video plugdev games netdev fuse www
This file has 464 bytes
Each method executes callbacks with a context (its this
) described in the next
section. Every method returns this
.
Whenever this()
is called with a non-falsy first argument, the error value
propagates down to the first catch
it sees, skipping over all actions in
between. There is an implicit catch
at the end of all chains that prints the
error stack if available and otherwise just prints the error.
The constructor function creates a new Seq
chain with the methods described
below. The optional arguments given become the new context stack.
Exactly like Seq(x, y...)
or Seq().extend([x,y...])
.
This is just another handy way for populating the stack.
The ap
is short for apply
.
This eponymous function executes actions sequentially.
Once all running parallel actions are finished executing,
the supplied callback is apply()
'd with the context stack.
To execute the next action in the chain, call this()
. The first
argument must be the error value. The rest of the values will become the stack
for the next action in the chain and are also available at this.args
.
If key
is specified, the second argument sent to this
goes to
this.vars[key]
in addition to the stack and this.args
.
this.vars
persists across all requests unless it is overwritten.
All arguments after cb
will be bound to cb
, which is useful because
.bind()
makes you set this
.
Use par
to execute actions in parallel.
Chain multiple parallel actions together and collect all the responses on the
stack with a sequential operation like seq
.
Each par
sets one element in the stack with the second argument to this()
in
the order in which it appears, so multiple par
s can be chained together.
Like with seq
, the first argument to this()
should be the error value and
the second will get pushed to the stack. Further arguments are available in
this.args
.
If key
is specified, the result from the second argument send to this()
goes
to this.vars[key]
.
this.vars
persists across all requests unless it is overwritten.
All arguments after cb
will be bound to cb
, which is useful because
.bind()
makes you set this
.
Catch errors. Whenever a function calls this
with a non-falsy first argument,
the message propagates down the chain to the first catch
it sees.
The callback cb
fires with the error object as its first argument and the key
that the action that caused the error was populating, which may be undefined.
catch
is a sequential action and further actions may appear after a catch
in
a chain. If the execution reaches a catch
in a chain and no error has occured,
the catch
is skipped over.
For convenience, there is a default error handler at the end of all chains. This default error handler looks like this:
.catch(function (err) {
console.error(err.stack ? err.stack : err)
})
Execute each action in the stack under the context of the chain object.
forEach
does not wait for any of the actions to finish and does not itself
alter the stack, but the callback may alter the stack itself by modifying
this.stack
.
The callback is executed cb(x,i)
where x
is the element and i
is the
index.
forEach
is a sequential operation like seq
and won't run until all pending
parallel requests yield results.
Like forEach
, call cb
for each element on the stack, but unlike forEach
,
seqEach
waits for the callback to yield with this
before moving on to the
next element in the stack.
The callback is executed cb(x,i)
where x
is the element and i
is the
index.
If this()
is supplied non-falsy error, the error propagates downward but any
other arguments are ignored. seqEach
does not modify the stack itself.
Like forEach
, calls cb for each element in the stack and doesn't wait for the
callback to yield a result with this()
before moving on to the next iteration.
Unlike forEach
, parEach
waits for all actions to call this()
before moving
along to the next action in the chain.
The callback is executed cb(x,i)
where x
is the element and i
is the
index.
parEach
does not modify the stack itself and errors supplied to this()
propagate.
Optionally, if limit is supplied to parEach
, at most limit
callbacks will be
active at a time.
Like seqEach
, but collect the values supplied to this
and set the stack to
these values.
Like parEach
, but collect the values supplied to this
and set the stack to
these values.
Create a new nested context. cb
's first argument is the previous context.
Recursively flatten all the arrays in the stack.
Like push
, but takes an array. This is like python's [].extend()
.
Set the stack to a new array.
Set the stack to [].
Executes an array operation on the stack.
Each callback gets executed with its this
set to a function in order to yield
results, error values, and control. The function also has these useful fields:
The execution stack.
The previous stack value, mostly used internally for hackish purposes.
A hash of key/values populated with par(key, ...)
, seq(key, ...)
and
this.into(key)
.
Instead of sending values to the stack, sets a key and returns this
.
Use this.into(key)
interchangeably with this
for yielding keyed results.
into
overrides the optional key set by par(key, ...)
and seq(key, ...)
.
this.args
is like this.stack
, but it contains all the arguments to this()
past the error value, not just the first. this.args
is an array with the same
indices as this.stack
but also stores keyed values for the last sequential
operation. Each element in this.array
is set to [].slice.call(arguments, 1)
from inside this()
.
This is used for error propagation. You probably shouldn't mess with it.
With npm, just do: npm install seq
or clone this project on github:
git clone http://github.com/substack/node-seq.git
To run the tests with expresso, just do:
expresso
This module uses chainsaw
When you npm install seq
this dependency will automatically be installed.
FAQs
Chainable asynchronous flow control with sequential and parallel primitives and pipeline-style error handling
The npm package seq receives a total of 15,731 weekly downloads. As such, seq popularity was classified as popular.
We found that seq 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
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.
Security News
Research
Socket's threat research team has detected five malicious npm packages targeting Roblox developers, deploying malware to steal credentials and personal data.