bill
bill
The problem that you will run into is that Later is a superset of Cron. It supports many more time periods (including custom ones) that cannot be translated to Cron....
Currently no. Some people have added timezone support using another library like timezone-js. You would need to update `date/timezone.js` to create timezone aware date instances.
Yes, this should be the way to go. You can search the issues for other people looking for timezone support.
If you added it as a build option so we could build versions with or without timezone support, than sure. Sort of like what I did to build the core...
This does work if you set Later to use your local timezone. The only scenario that doesn't work is if you want to use an arbitrary timezone. I'd be happy...
Are you using webpack?
I don't use Meteor so I'm not sure what the problem could be.
You can use a Later exception schedule with the full date constraint to make certain absolute time periods unavailable: ``` later.parse.recur().except().on(new Date('2013-03-21T11:30:00')).fullDate() ``` Or if you want to just make...
May need to add a valid schedule to your exception schedule (recur().every(1).minutes().except()...). You should use Laterjs to validate the resource schedule to make sure it produces what you think it...
The `after` constraint is inclusive and the `before` constraint is exclusive. Anything between 6:30:00 and 6:59:59 will be considered conflicting.