cron-parser breaking changes
Every breaking API change we have recorded in cron-parser on npm: 25 breaking changes in 1 version. Below are its newest version, removals and renames first, each with its source.
Newest change February 13, 2025
On this page
5.0.0
- Removed
The minimum supported Node.js version is now 18. Users on older Node.js versions must upgrade before using this release. github.com - Removed
CronExpression.iterate
CronExpression.iterate was removed in cron-parser 5.0.0 npmjs.com - Removed
CronFields
CronFields was removed in cron-parser 5.0.0 npmjs.com - Removed
CronParser
Crontab file parsing is now done with the standalone CronFileParser class instead of CronParser. github.com - Removed
DateType
DateType was removed in cron-parser 5.0.0 npmjs.com - Removed
DayOfTheMonthRange
DayOfTheMonthRange was removed in cron-parser 5.0.0 npmjs.com - Removed
DayOfTheWeekRange
DayOfTheWeekRange was removed in cron-parser 5.0.0 npmjs.com - Removed
fieldsToExpression
fieldsToExpression was removed in cron-parser 5.0.0 npmjs.com - Removed
parseExpression
parseExpression was removed in cron-parser 5.0.0 npmjs.com - Removed
parseFile
parseFile was removed in cron-parser 5.0.0 npmjs.com
And 15 more in this version.
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.
Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp