Cron expressions are hard to read — so I built cronread

The problem

Developers routinely have to leave the terminal and visit crontab.guru to verify what a cron expression actually schedules — there is no zero-dependency CLI tool that explains cron syntax and shows upcoming run times inline.

If you've hit this before, you know how it goes — you switch tabs, paste the expression into crontab.guru, then switch back. Every. Single. Time.

As a solution, I created cronread

Explain a cron expression in plain English and show the next N scheduled run times

It's zero-dependency Node.js, so you can run it immediately without installing anything:

npx cronread "*/15 9-17 * * 1-5"

Output:

$ npx cronread "*/15 9-17 * * 1-5"

  Pattern : */15 9-17 * * 1-5
  Schedule: every 15 minutes, between 9:00 and 17:00, on Monday to Friday

  Next 5 runs (local time):
    1. 2026-05-12 Tue 09:15
    2. 2026-05-12 Tue 09:30
    3. 2026-05-12 Tue 09:45
    4. 2026-05-12 Tue 10:00
    5. 2026-05-12 Tue 10:15

How it works

Pure Node.js with no dependencies: parses each field (ranges, steps, lists, wildcards) into value sets, walks forward minute by minute from the current time to find the next N matching timestamps, and renders the results as clean terminal output.

Why I built it

Found recurring threads on r/devops and r/node where developers debate what cron expressions actually schedule, often resorting to crontab.guru mid-terminal-session. The most popular npm cron packages (node-cron, cron) are runtime schedulers, not expression explainers — none expose a zero-dep CLI that translates a schedule to plain English. The gap between a website you have to open and a command you can run is exactly the kind of friction a micro-tool eliminates, and cron syntax is something every developer hits regardless of stack.

---

Part of µ micro — one new developer CLI tool, shipped every day. All tools are zero-dependency Node.js and run instantly with npx.