Please someone do this, it’d be indeed be a big blow to our current architecture if this would be true.
I don’t actually understand why it should be the case, code-wise. Calling Methods from the server was always supported and why shouldn’t it work as before, with one async method awaiting the next (or not), as required.
I haven’t really started working on the migration though. We’ll start piecemeal in January I think.
I tried to start a fresh Meteor 2.9 with DISABLE_FIBERS flag but
the app crash:
TypeError: self._nextObjectPromise(...).await is not a function
at SynchronousCursor._nextObject (packages/mongo/mongo_driver.js:1154:38)
at SynchronousCursor.forEach (packages/mongo/mongo_driver.js:1168:22)
at SynchronousCursor.map (packages/mongo/mongo_driver.js:1178:10)
at SynchronousCursor.fetch (packages/mongo/mongo_driver.js:1202:17)
at Cursor.<computed> [as fetch] (packages/mongo/mongo_driver.js:937:32)
at MongoConnection.findOne (packages/mongo/mongo_driver.js:812:56)
at OplogHandle._startTailing (packages/mongo/oplog_tailing.js:231:57)
at new OplogHandle (packages/mongo/oplog_tailing.js:85:8)
at new MongoConnection (packages/mongo/mongo_driver.js:210:25)
at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collection_driver.js:4:16)
at Object.<anonymous> (packages/mongo/remote_collection_driver.js:51:18)
at Object.defaultRemoteCollectionDriver (packages/underscore.js:784:19)
at new Collection (packages/mongo/collection.js:110:40)
at module (imports/api/links.js:3:32)
at fileEvaluate (packages/modules-runtime.js:336:7)
at Module.require (packages/modules-runtime.js:238:14)
Exited with code: 1
Your application is crashing. Waiting for file change.
It looks like 2.9.0 is not ready to run without fibers