cron-parser
cron-parser copied to clipboard
harrisiirak
Node.js library for parsing crontab instructions
Hi, the expression `0 12 1-31 * 1` should output dates that match every day-of-month **and** day-of-week since both fields are not `*`, but it outputs the same as `0...
 It encounted an error: Invalid expression, loop limit exceeded cron = "0 0 1L */12 *" ``` const interval = parser.parseExpression(cron, { startDate: new Date(), currentDate: new Date(), iterator:...
I noticed that `next()` skips a day when `prev()` was called before, even if `reset()` has been called. Here is a test case, tested with [email protected]. Local TZ is Europe/Paris...
We recently upgraded the module from 2.3.7 to 4.6.0 and saw a huge performance degradation. When calling the `next()` method 10000 times, our benchmark went from 5000ms to 68000ms. Will...
This pull request introduces a complete refactor of the codebase into TypeScript, maintaining compatibility with the documented API. Users should not experience any breaking changes, however, those relying on undocumented...
Given a cron expression `* 6-20 * * *`, at `6:01`. I expect `.prev()` to be `6:00` and then `.next()` to be `6:01`. Actually `.prev()` is `6:00` as expected but...
Just a thought. Instead of `while(true)` inside the example for 'Iteration with limited timespan' you could use `while(iterator.hasNext())` imho this would give you a clean exit condition instead of relying...
``` const cron = '12 0 6 * * *'; console.log(parseString(cron).expressions[0]. fields); ``` 控制台结果: ``` dayOfMonth: [6] dayOfWeek: [0, 1, 2, 3, 4, 5, 6, 7] hour: [0] minute: [12]...
I encountered an issue that left me scratching my head for a good while... When stringifying a cron expression that contains 6 fields accoring to the readme, the result is...
Metadata
Owner
Metadata
Node.js library for parsing crontab instructions