You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Will this package be updated to be compatible with the new Meteor 3.0 update? Currently, I have to comment out the api.versionsFrom call in package.js to make it work, as well as changing lines 90 and 94 in synced-crron-server.js to SyncedCron._collection.createIndex({intendedAt: 1, name: 1}, {unique: true}); and SyncedCron._collection.createIndex({startedAt: 1 }, respectively.
This is likely part of the larger effort to address #147
Thanks
The text was updated successfully, but these errors were encountered:
Hi ! As most of us are looking into meteor 3.0 migration and use this package, would it be possible to merge the related PR into master ? This will prevent numerous forks or local packages fixed. Thank you.
If you can't maintain it anymore, please tell us, so we can move the repo into community packages.
I'm using kolyasya:oplog-keep-awake which relies on this package, @kolyasa how do you expect to manage this as you started 3.0 migration ?
Hello,
Will this package be updated to be compatible with the new Meteor 3.0 update? Currently, I have to comment out the
api.versionsFrom
call inpackage.js
to make it work, as well as changing lines 90 and 94 insynced-crron-server.js
toSyncedCron._collection.createIndex({intendedAt: 1, name: 1}, {unique: true});
andSyncedCron._collection.createIndex({startedAt: 1 },
respectively.This is likely part of the larger effort to address #147
Thanks
The text was updated successfully, but these errors were encountered: