I remember working on waterfall projects, when the whole thing was 95% done for months at a time. This leaves the customer extremely untrusting of the IT delivery team, as there is no change to measure. However, if you can persuade them to break down their requirements into prioritised ...
{ location =currentURL }) .evaluate(function(selector) { return { html: $(selector).html() } }, 'html') .then(function(data) { data.location = location; horseman.close(); waterfallCallback(null, data); }) .catch(function(data) { horseman.close(); return waterfallCallback(true); ...
as well as some common patterns\nfor asynchronous control flow (parallel, series, waterfall…). All these\nfunctions assume you follow the node.js convention of providing a single\ncallback as the last argument of your async function.\n\n\n## Quick Examples\n\njavascript\nasync.map([\'...