fix: OR day-of-month and day-of-week when a field is a full-coverage range

[spokodev]

Problem

Per crontab(5):

If both fields are restricted (i.e. do not contain the * character), the command will be run when either field matches.

The criterion is the literal * character, not whether the value-set covers every value. node-cron breaks this when one day field is a full-coverage range or step (1-31, 0-6, */1, 0,1,...,6) instead of a literal *.

Repro

Expression 0 0 12 1-31 * 1 (day-of-month = 1-31, day-of-week = Monday), starting 2026-06-01T00:00:00Z, UTC:

Implementation	Result
node-cron (current)	Jun 1, 8, 15, 22 (only Mondays) — wrong
cron-parser 5.6.1	Jun 1, 2, 3, 4 (every day)
croniter 6.2.2	Jun 1, 2, 3, 4 (every day)

Both 1-31 and 1 are restricted (neither is *), so the two day fields are OR'd and the job runs every day. node-cron applies AND and fires only on Mondays.

Root cause

getNextDateFrom in src/time.ts decides whether each day field is "restricted" by cardinality:

Object.keys(this.dayOfMonth).length !== 31
Object.keys(this.dayOfWeek).length !== 7

That is a proxy for "the field is not *". A full-coverage range such as 1-31 has full cardinality yet is not *, so the proxy misclassifies it as a wildcard and falls back to AND. The parser never recorded whether the raw token was literally *.

Fix

• Capture dayOfMonthWildcard / dayOfWeekWildcard at parse time, set when the raw field contains the * character (before the * to low-high expansion).
• Use those flags in the day-advance condition instead of the cardinality checks.

This keys the OR/AND decision on the * character exactly as crontab(5) specifies. */1 and other step-wildcards keep their existing wildcard treatment because they contain *.

Tests

Added a crontime test asserting 0 0 12 1-31 * 1 fires Jun 1, 2, 3, 4 from 2026-06-01. It fails on main (returns Jun 1, 8, 15, 22) and passes with the fix. Full suite stays green (162/162 under TZ='Europe/Paris').