Skip to content

Commit

Permalink
make flow control docs more standalone
Browse files Browse the repository at this point in the history
Hopefully, this change reduces confusion for folks reading the flow control docs after being directly linked to them, without having read the preceding sections of the README
  • Loading branch information
mikermcneil authored May 2, 2020
1 parent d6b9417 commit f577065
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -445,9 +445,9 @@ If you're using Node >= v7.9, you're in luck. With `await`, flow control works

##### What if I'm stuck with an old version of Node.js?

Sorry to hear that... Once again, `await` solves all of these problems too. It's the biggest boon to JavaScript development since Node.js was released.
Sorry to hear that... Once again, `await` solves all of these problems. It's the biggest boon to JavaScript development since Node.js was released. You'll wish you could use it.

But don't worry- this section's for you. Since Node.js is asynchronous, when using Node < v7.9, seemingly-tricky flow control problems often arise in practical, userland code. Fortunately, they're solveable when equipped with the proper tools and strategies.
But don't worry- this section is for you. Since Node.js is asynchronous, when using Node < v7.9, seemingly-tricky flow control problems often arise in practical, userland code. Fortunately, they're solveable when equipped with the proper tools and strategies.

> Most of the examples below use simple Node callbacks, but note that many similar affordances are available for promise-chaining -- for example, check out `.toPromise()` ([below](#toPromise)) and `Promise.all()` (in bluebird, or native in ES6, etc.). The concepts are more or less the same regardless.
>
Expand Down

0 comments on commit f577065

Please sign in to comment.