Add firstRunPromise

docs/generators/changelog/versions/2.14.md

@@ -25,15 +25,15 @@ Hacktoberfest release! 🎉
 #### Migration Steps
 
 ##### Android splash screen
-If you have been using `splash-screen` for Cordova, you need to update your code as Android changed their splash screen API, 
-the `cordova-plugin-splashscreen` is now on `cordova-android` core, so we have removed the dependency from the `splash-screen` 
+If you have been using `splash-screen` for Cordova, you need to update your code as Android changed their splash screen API,
+the `cordova-plugin-splashscreen` is now on `cordova-android` core, so we have removed the dependency from the `splash-screen`
 package. As a result we are dropping the support for dark mode splash screen on Android.
 
 To create this now you need to create two themes on your `config.xml` file.
 
->  Note that it's still possible to have it by adding the according themes with App.appendToConfig and App.addResourceFile - but this is not something Meteor will do automagically right now.
+>  Note that it's still possible to have it by adding the according themes with App.appendToConfig and App.addResourceFile - but this is not something Meteor will do automatically right now.
 
-TODO: @matheusccastroo sample on how the new config should look and link to relevant Cordova docs 
+TODO: @matheusccastroo sample on how the new config should look and link to relevant Cordova docs
 
 ## Breaking Changes
 
@@ -55,7 +55,7 @@ TODO: @matheusccastroo sample on how the new config should look and link to rele
   - Updated `semver` to v7.5.4
   - Updated `@meteorjs/babel` to v7.18.4
   - Cordova has been updated to v12.0.1 for Android and v7.0.1 for iOS
-  - `meteor create` command was re-made to be more interactive 
+  - `meteor create` command was re-made to be more interactive
 
 ## Meteor Version Release
 
@@ -113,7 +113,7 @@ TODO: @matheusccastroo sample on how the new config should look and link to rele
   - Added `appleMail` user agent to allow modern bundle on iPads
 
 * `mongo@get-version`
-  - Added deprecation messages into type definitions 
+  - Added deprecation messages into type definitions
   - Fix ObjectIDs handling in oplogV2V1Converter
 
 * `modules@get-version`
@@ -166,7 +166,7 @@ TODO: @matheusccastroo sample on how the new config should look and link to rele
   - Remove logging request/response in google_server
 
 * NPM `@meteorjs/babel@7.18.4`
-  - Updated `@meteorjs/reify` to v0.24.1 
+  - Updated `@meteorjs/reify` to v0.24.1
 
 * NPM `@meteorjs/babel-preset-meteor@7.10.1`
   - Add Facebook in-app browser

docs/source/api/tracker.md

@@ -80,7 +80,7 @@ If the initial run of an autorun throws an exception, the computation
 is automatically stopped and won't be rerun.
 
 ### Tracker.autorun and async callbacks
-`Tracker.autorun` can accept an `async` callback function.  
+`Tracker.autorun` can accept an `async` callback function.
  To preserve reactivity for the reactive variables inside the async callback function, you must use a `Tracker.withComputation` call as described below:
 
 {% apibox "Tracker.withComputation" %}
@@ -94,7 +94,7 @@ Tracker.autorun(async function example1(computation) {
 
   // Code after the first await looses Tracker.currentComputation: no reactivity.
   reactiveVar2.get(); // This won't trigger a rerun.
- 
+
   // You can bring back reactivity with the Tracker.withCompuation wrapper:
   let users = await Tracker.withComputation(computation, () => Meteor.users.findAsync({}).fetch());
 
@@ -112,7 +112,7 @@ The `react-meteor-data` package uses `Tracker.withComputation` to make the `useT
 More can be seen [here](https://github.com/meteor/react-packages/tree/master/packages/react-meteor-data#maintaining-the-reactive-context)
 
 ### Using async callbacks in versions of Meteor prior to 2.10
-`Tracker.autorun` can accept an `async` callback function.  
+`Tracker.autorun` can accept an `async` callback function.
 However, the async call back function will only be dependent on reactive functions called prior to any called functions that return a promise.
 
 Example 1 - autorun `example1()` **is not** dependent on reactive changes to the `Meteor.users` collection.  Because it is dependent on nothing reactive it will run only once:
@@ -306,7 +306,7 @@ computation has logic specific to the first run.
 
 `Computation.firstRunPromise` will be set to the result of the call of the autorun function after the initial computation has been completed. If the autorun function is an async function, it'll then contain its promise, thus making the completion of the execution await-able. That allows us to manually synchronize autoruns like this:
 
-```js  
+```js
 
 await Tracker.autorun(async () => {
   await Meteor.userAsync();
@@ -320,9 +320,9 @@ await Tracker.autorun(async () => {
 
 ```
 
-For a better developer experience `firstRunPromise` is automagically appended to your async `autorun` calls so you don't have to write them yourself. Meaning this also works: 
+For a better developer experience `firstRunPromise` is automatically appended to your async `autorun` calls so you don't have to write them yourself. Meaning this also works:
 
-```js  
+```js
 
 await Tracker.autorun(async () => {
   await Meteor.userAsync();