Error: Can't set timers inside simulations?

[trusktr]

I sometimes get this error on the front end. However I am not setting timeouts anywhere. I am using the new async methods inside Meteor.methods.

Basically the only method I have is this (on both sides, but I’ve learned that Meteor.methods are no longer good for simulations and isomorphic code like old code used to be before non-async methods were removed):

Meteor.methods({
	async 'visits.increment'(route: string) {
		console.log('VISITS INCREMENT')
		await Visits.upsertAsync({route}, {$inc: {visits: 1}})
		console.log('UPDATED:', (await Visits.findOneAsync({route})).visits)
	},
})

[trusktr]

This is slightly related to

Synchronous Collection methods removed from Meteor, now we need async signals

Removing synchronous collection methods from the backend is Meteor’s biggest hurdle (I wonder how many apps have yet to migrate?). Without the old Fibers-based “synchronous” APIs, we are missing one very grand thing in Meteor: Isomorphic reactive code In lieu of this, it would be great if Meteor would gain new signals-and-effects patterns (reactivevar-and-tracker.autorun patterns) for handling async values. The issue: Promises are not repeatable, whereas signals are. This makes a world of di…

In the past, we were able to write isomorphic methods very easily. Now we are not, and the problem I have is probably because I should no longer have the method on the client-side (no longer isomorphic).

[jam]

but I’ve learned that Meteor.methods are no longer good for simulations and isomorphic code

You can write isomorphic code with the *Async suffix inside Meteor.methods.

Hmm I can’t reproduce the error you’re seeing based on your code sample above. What am I missing? What version of Meteor are you using?