cron-parser icon indicating copy to clipboard operation
cron-parser copied to clipboard

Node.js library for parsing crontab instructions

Results 44 cron-parser issues
Sort by recently updated
recently updated
newest added

是不是不支持 typescript 4.1+ 能不能添加 支持

https://github.com/harrisiirak/cron-parser/blob/ec7a3844553d93bddac34d07c06245eae5579829/lib/field_stringify.js#L27-L28

bug

Hello, Is there a method to get last date of an expression (with a endDate option set)? Thanks for your help

## User Story 👥 Here there :wave: :wave:. I was initially evaluating using this library for the following use case: - an API sends me a cron string - I...

enhancement

Hello, I am trying to use `cron-parser` in a UI environment where the user can toggle days of the week on and off. The result of the UI is a...

bug

Steps to reproduce: ``` const parser = require('cron-parser'); let interval; // the following call prints `'2020-11-01T06:10:00.000Z'` interval = parser.parseExpression('* 10 1 * * 0', { tz: 'America/Toronto', currentDate: '2020-11-01T06:00:00.000Z' ,...

bug

Currently, adding the optional year segment to the cron expression breaks parsing. Will support for this be added in the future? (ie `0 0 14 ? * MON *`)

feature-request

https://github.com/harrisiirak/cron-parser/blob/f687555f25ff0e4e12a951f3a4827b382436692f/lib/expression.js#L275 Due to not providing basic repeat atomic format validation, cron-parser sees format like `10 16/17/18 * * *` as valid, and parse it as `10 16/17 * * *`....

bug

http://www.quartz-scheduler.org/documentation/quartz-2.3.0/tutorials/crontrigger.html Cron expression like ```0 0 0 2,3,L * ?``` should be invalid.