Hello everyone, in order to enable the anticipation of application migration, asynchronous versions of functions related to calls to Mongo were introduced from version 2.10 onwards. This was implemented by returning a Promise.resolve(…). However, within the Meteor core, synchronous calls to Mongo are still considered. To migrate some packages, such as cultfcoders:redis-oplog or matb33:collection-hooks, it is necessary to have an asynchronous implementation in the Meteor core. Do you think we will be able to migrate these packages only after the release of version 3.0? Does anyone see any criticality in the future migration of these packages?
Regarding the accounts package, which is often used for custom implementations, the same problem exists: the internal calls are still synchronous, but I assume that they will also have to become asynchronous.