Skip to content

Switch scheduling backend to Croner #1164

@Hexagon

Description

@Hexagon

Is there an existing issue that is already proposing this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe it

NPM package cron is broken in many ways, which you can read about here. It doesn't receive much (if any) attention. Have a look at their list of issues.

Describe the solution you'd like

I would recommend you to consider switching from npm package cron to croner.

Teachability, documentation, adoption, migration strategy

I noticed that you have implemented one feature of cron, which isn't supported by croner - the utcOffset. I could implement that if you're interested and think it is a useful feature. So far i've avoided giving that option, as time zones can have different utc offset at different time of year.

What is the motivation / use case for changing the behavior?

Croner is actively maintained, trusted by pm2, and have 0 active issues.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions