refactor: prefer using app.whenReady() #21972
Merged
+111
−109
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
In the docs, specs, and lib, replace instances of
app.once('ready', ...)
(seen occasionally) andapp.on('ready', ...)
(very common) withapp.whenReady().then(...)
.The goal of this small change is to encourage new users to use whenReady():
Checklist
npm test
passesRelease Notes
Notes: no-notes