@wolfstar/plugin-scheduled-tasks. The plugin runs tasks later or on a schedule, storing their jobs in Redis through BullMQ so they survive restarts and are shared by every process of your bot. For the weekly summary across all packages, see the changelog overview.
0.3.0 (2026-10-20)
New features
- Own
stars.configkey — The module setsmeta.configKey, so you can write its options under the top-levelscheduledTaskskey ofstars.configinstead of the[specifier, options]tuple ofmodules. The tuple still works and is merged over the key. The key is typed indefineConfigonce the module is imported instars.config.ts. (#259)
Updates
- New optional peer —
@wolfstar/schema(^0.9.0) is a new optional peer that carries theStarsConfigtype the keys extend.
Migration
@wolfstar/kitpeer raised — The@wolfstar/kitpeer range moves from^0.1.0to^0.2.0, the first version that readsconfigKey. If your project uses@wolfstar/kit0.1, update it.
0.2.0 (2026-10-07)
New features
- Readiness gate — Give the plugin a
readycallback (with optionalreadyTimeoutandreadyDelay) and setwaitForReady: trueon tasks that need your app to be up. A job taken before the app is ready waits. If the timeout passes, the job moves back todelayedinstead of failing, so it costs no attempt and emits noscheduledTaskError. (#228) scheduledTaskNotReadyevent —ScheduledTaskEvents.ScheduledTaskNotReadyreports a job that timed out waiting for readiness.ScheduledTaskHandler#waitForReady()— Lets a task wait for readiness by hand.- Job and token in
run—ScheduledTaskHandler#runtakes an optional second argument with the BullMQ job and token.
0.1.0 (2026-10-04)
New features
- New package — Scheduled tasks for
@wolfstar/http-framework, the counterpart of@sapphire/plugin-scheduled-tasks. Tasks areScheduledTaskpieces run by a BullMQ worker. Create them withcontainer.tasks.create(), or repeat them on anintervalor cronpattern. List the package inmodulesinstars.config, or passscheduledTasks()toplugins. See the package docs. (#177)