The "old API" warning is unclear about what new API to use instead.

[striezel]

The migration guide for Meteor 2.12 mentions a way to enable warnings about an old API, so out of curiosity I enabled it on my project. It looks like every use of methods like remove, insert or findOne (and maybe others, too) on MongoDB collections trigger that warning. That's fine so far, because it informs me what will be removed in Meteor 3.

However, neither the warning nor the migration guide mention what API should be used instead. That makes the warning kind of pointless, because even if I am willing to migrate to a newer API, I do not have any idea what API that should be. So I checked the documentation on collections and it looks like insert etc. are still the way to use MongoDB collections. 🤔

So the question is: What should Meteor users use instead, any why does the documentation not contain a pointer to the new API? That would make migration easier.

[ToyboxZach]

There are new *async versions of each method that should be used

remove -> removeAsync
insert -> insertAsync

etc
On the server you will now have to await each result as fibers is being removed

[striezel]

Good to know.

This move to asynchronous versions should also be mentioned in the migration guide and the documentation for Mongo.Collection. Otherwise people will probably still keep using the old versions of those methods.

[Grubba27]

I think the only docs about those methods are in 2.8 migration guide. Will make this a docs issue for this reason.
Will close this one as I think it is "solved" and create another one regarding these missing docs. Sounds good?

[striezel]

I think the only docs about those methods are in 2.8 migration guide. Will make this a docs issue for this reason. Will close this one as I think it is "solved" and create another one regarding these missing docs. Sounds good?

Yes, #12650 together with #12649 should solve this.