Security News
The Risks of Misguided Research in Supply Chain Security
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
ff simplifies the most common use cases for series, parallel, and promise utilities. It was built because existing async libraries are too verbose and don't handle errors properly. Don't let your errors go unhandled. :-)
npm install ff
lib/ff.js
to your HTML page.Here's a brief example that shows both serial and parallel steps:
var f = ff(this, function () {
fs.readFile("1.txt", f());
fs.readFile("2.txt", f());
}, function (fileA, fileB) {
concatFiles(fileA, fileB, f());
}, function (result) {
f(result.toUpperCase());
}).cb(cb);
A typical Express web handler looks like this. (Note that even if an exception gets thrown during one of these handlers, it gets passed down the chain as an error.)
function (req, res, next) {
var f = ff(function() {
authenticateUser(req, f());
}, function (user) {
f(user); // pass the user along synchronously
user.getFriends(f());
}, function (user, friends) {
res.json({ user: user, friends: friends });
}).error(next); // call next() *only* on error
}
ff
and save its return value (as f
, perhaps).var f = ff([context], stepFunctions... )
The ff
function takes a context and any number of
functions, which we call "steps". Each step is run one at a time. Use
ff
's return value (often called f
) to create callbacks for any
async functions used in each step.
f
object inside each step function.Within your step functions, pass f()
as the callback parameter to
any async function. This reserves a "slot" in the next step's
function arguments. For instance:
fs.readFile("1.txt", f()); // fs.readFile will use that as a callback.
Most often, that's all you'll need, but there are other ways to pass data:
f(data); // pass data synchronously to the next function
fs.exists("1.txt", f.slotPlain()); // fs.exists doesn't pass (err, result), just (result)
emitter.once("close", f.wait()); // just wait for the "close" event
f
:f()
Calling f()
reserves a slot in the next step's function arguments,
and returns a callback that you should pass into an async function.
The async function should be called with an error as in callback(err, result)
. This is an alias for f.slot()
.
f(arg1, arg2...)
If you call f
with arguments, those arguments will be passed into
the next step. This can be useful when you need to pass along a value
directly to the next function synchronously. This is an alias for
f.pass()
.
f.wait()
Sometimes you don't want to pass any arguments to the next function,
but you just want to wait until an async call completes successfully.
This behaves exactly like f()
and f.slot()
, handling errors, but
no arguments are passed to the next step.
f.slotPlain()
This is like f()
and f.slot()
, except that the resulting callback
must not accept an error, as in callback(result)
. Node's
fs.exists
doesn't return an error, for instance, and so you must use
f.slotPlain()
for its callback instead. (If you had used
f.slot()
, it would have thought fs.exists
had passed an error as
the first argument.
f.waitPlain()
See f.slotPlain()
. Like f.wait()
, this does not pass any
arguments to the next step.
f.group()
This reserves exactly one slot in the next step, and returns a group object that has all of the above methods. Anything you slot or pass into the group gets passed into the next function's argument list as an array. (See the Groups example.)
.cb
, .error
, .success
)After you've called ff()
with your steps, you'll want to handle the
final result that gets passed down the end of the function. We often
do this like so:
var f = ff(
// steps here...
).cb(cb);
That final callback will be passed arguments node-style: cb(err, results...)
. (The number of arguments after err
depends on how many
slots you've passed from the last function in the chain.) This lets
you use ff within any part of your code without expecting any other
function to know that ff
exists in your own code.
There are three ways you can handle the final result (you can mix and match):
f.cb( function (err, results...) { } )
A .cb()
result handler will always be called, whether or not an
error occurred. An error object will be passed first (null if there
was no error.)
f.success( function (results...) {} )
A .success()
handler will only be called if no error occur ed.
Additionally, an error object will not be passed. Only results.
f.error( function (err) {} )
A .error()
result handler will only be called if an error occured.
In this case, err
will never be null. (If you're using Express,
often we use .error(next)
to propagate whenever we didn't reach a
call to res.send()
.)
Always remember to add either a .cb()
or .success()
handler
after your ff()
call, so that errors propagate!
If any function throws an exception, or an error gets passed to one of
the callbacks (as in callback(err, result)
), the error will get
passed down to the next function that can handle the error. In most
cases, this is the .cb(cb)
function you added at the end. This is an
important feature that a lot of async libraries don't handle properly,
and it ensures that if you specify a .cb()
or .error()
, you'll
always pass back a final callback with an error or a result.
The f.group()
method reserves exactly one slot in the next step and
returns an object just like f
. Anything you slot or pass into the
group gets passed into the next function's argument list as an
array. This is useful for processing arrays of items. Here's an example:
var allMyFiles = ["one.txt", "two.txt", "three.txt"];
var f = ff(function() {
var group = f.group();
allMyFiles.forEach(function (file) {
fs.readFile(file, group());
});
}, function (allFiles) {
// allFiles now consists of 3 items (the contents of each file).
// If any call had returned an err, this function would not be
// called, and the error would have been passed down to `cb`.
}).cb(cb);
The following are equivalent:
var f = ff(this,
one,
two,
).cb(three);
var f = ff(this);
f.success(one);
f.success(two);
f.cb(three);
Error handling is actually quite simple: If an error occurs in any
step, it gets passed down, skipping over any .success
handlers.
Let's say you want to do something simple: Read two files, and callback whether or not the two files are equal. And we want any errors to be propagated up to the caller.
function compareFiles(pathA, pathB, cb) {
var f = ff(function () {
fs.readFile(pathA, f());
fs.readFile(pathB, f());
}, function (fileA, fileB) {
f(fileA == fileB); // pass the result to cb
}).cb(cb);
}
function compareFiles(pathA, pathB, cb) {
var callback = new lib.Callback();
fs.readFile(pathA, callback.chain());
fs.readFile(pathB, callback.chain());
callback.run(function (chains) {
var err = chains[0][0] || chains[1][0];
if (err) {
cb(err);
} else {
cb(null, chains[0][1] == chains[1][1]);
}
});
}
function compareFiles(pathA, pathB, cb) {
async.parallel({
fileA: function (callback) {
fs.readFile(pathA, callback);
},
fileB: function (callback) {
fs.readFile(pathB, callback);
}
}, function (err, results) {
if (err) {
cb(err);
} else {
cb(null, results.fileA == results.fileB);
}
});
}
function compareFiles(pathA, pathB, cb) {
var wait = common.parallel(function(results) {
var err = results.err1 || results.err2;
if (err) {
cb(err);
} else {
cb(null, results.fileA == results.fileB);
}
});
fs.readFile(pathA, wait('err1', 'fileA'));
fs.readFile(pathB, wait('err2', 'fileB'));
}
var f = ff(function () {
request("POST /auth/", f());
}, function (userID) {
request("GET /users/" + userID, f());
}, function (userInfo) {
request("POST /users/" + userInfo.id, {name: "Spike"}, f.wait());
}, function () {
// all done!
}).cb(cb);
If you have better examples, please submit them!
This code was originally based on Tim Caswell's sketch of a reimagined Step library.
FAQs
Concise, Powerful Asynchronous Flow Control in JavaScript.
We found that ff demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 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.
Security News
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.