'fast-async' is a Babel v6.x.x plugin that implements the ES7 keywords
await using syntax transformation
at compile-time, rather than generators.
The main reason for using 'fast-async' as opposed to Babel's default implementation of async/await is performance (https://github.com/MatAtBread/nodent#performance) - it's 3-4 times faster in a browser/node, and as much as 10 times faster on a mobile browsers, mainly due to avoiding generators (and therefore regenerator).
There's a simple test (that just makes sure the plugin works and generates code that runs). More complete test coverage is included with nodent.
Because Babel parses the code, the ES7 extensions possible with nodent (
async return and
async throw) are not supported, however full implementation of
async function containing
await expressions is implemented.
For Babel v5.x.x install email@example.com
v6.1.x fast-async@>=6.1.0 can use nodent v2 or v3 (and acorn v3 or v4). Nodent v3 has the option of generating code with Promises which needs no runtime at all, at the cost of size and speed. v6.1.x can also reference the runtime via an import (useRuntimeModule option), rather than include the source inline.
npm install fast-async --save
Just include the plugin to the babel options. Minimal
That's all. Neither
babel-polyfill required. Your application, once compiled, will probably needs nodent's runtime = see below.
"plugins":"fast-async""env":"augmentObject": false"dontMapStackTraces": true"dontInstallRequireHook": true"compiler":"promises": true"generators": false"runtimePattern":null"useRuntimeModule":false
From the installation directory (e.g. node_modules/fast-async):
The plugin accepts the following options object, which itself is optional, as are all members. These are based on the options in nodent, but since much of the parsing is done by Babel some are unused.
env:, // Supplied routine to emit transformation warnings. Default: console.logaugmentObject:false, // Add the nodent utilities asyncify() and isThenable() to Object.prototypedontMapStackTraces:true, // Don't install the stack trace hook that maps line numbers (default: true)dontInstallRequireHook:false // Don't transform all JS files as they are loaded into node (default: true)}compiler:promises:true // Use nodent's "Promises" mode. Set to false if your execution environment does not support Promises.generators:false // Transform into 'Generators' (sub-optimal, but it works)runtimePattern:null // See belowuseRuntimeModule:false // See below
For more information on the compiler options, see ES7 and Promises in the nodent documentation.
6.1.x The dontMapStackTraces now defaults to
trueas having both nodent and babel map stack traces doesn't work well
By default, fast-async will put the nodent runtime into every file containing an
async function or
If your project is made up of more than one file, the constant redefinition of the runtime is a waste of time and space. You can
specify that you want the runtime in particular file(s) by setting the 'runtimePattern' to a regular expression (in quotes).
Only files that match the regular expression will have the runtime defined (which is global, so you only need it once).
Note: At least one of the file(s) matching the "runtimePattern" must use either
async as the runtime function (or
require('nodent-runtime') if you set
"useRuntimeModule":true) is only included for files that reference it.
Alternatively, if you set runtimePattern to
"directive", the statement
"use runtime-nodent"; will be replaced with the runtime during compilation.
v6.1.x If you specify the option
"useRuntimeModule":true, the runtime is not included directly as source, but via an import of nodent-runtime, which is typically resolved to
require()by babel. The nodent-runtime module must be added as a dependency in your target project. The runtime need only be included once in your entire project, and should precede any code that uses async or await.
Online performance checkers: