Skip to content

MonthlyEvent

MONTHLY - Recurring events on the same day every month Supports intervals, month exclusions, and date exclusions.

// Every 15th of the month
{ type: "monthly", id: "payday", day: 15 }
// Quarterly (every 3 months starting January)
{ type: "monthly", id: "quarterly-review",
day: 1, interval: 3, startMonth: 1 }
// Monthly except December
{ type: "monthly", id: "team-lunch",
day: 10, excludeMonths: [12] }

TMetadata extends Record<string, unknown> = Record<string, unknown>

Custom metadata type extending Record<string, unknown>

TCategory extends string = string

optional allDay?: boolean

BaseEventProperties.allDay


optional categories?: TCategory[]

BaseEventProperties.categories


optional color?: string

BaseEventProperties.color


day: number

Day of the month. 131, or negative to count from the end (-1 = last day of every month, -2 = second-to-last). Note: a positive day past the month’s length (e.g. 31 in February) is skipped for that month.

15 // 15th of each month
-1 // last day of every month

optional description?: string

BaseEventProperties.description


optional duration?: number

BaseEventProperties.duration


optional endDate?: string

BaseEventProperties.endDate


optional endTime?: string

BaseEventProperties.endTime


optional exceptions?: EventExceptions

Per-occurrence exceptions keyed by the event’s ORIGINAL computed date (YYYY-MM-DD) — maps ICS EXDATE / RECURRENCE-ID. { skip: true } drops that occurrence; { override } replaces properties for that one instance.

BaseEventProperties.exceptions


optional excludeDates?: string[]

Specific dates to exclude (ISO format: YYYY-MM-DD)

["2025-12-15"] // Skip this specific date

optional excludeMonths?: number[]

Months to exclude (1-12)

[7, 8] // Skip July and August

optional icon?: string

BaseEventProperties.icon


id: string

BaseEventProperties.id


optional interval?: number

Recurrence interval in months (default: 1)

3 // Every 3 months (quarterly)

optional keywords?: string[]

BaseEventProperties.keywords


optional location?: string

BaseEventProperties.location


optional metadata?: TMetadata

BaseEventProperties.metadata


optional onConflict?: ConflictResolver

Conflict resolver for handling events on the same day. Called during event generation to determine action when this event would occur on a specific date.

Default behavior (when not specified): keep all events

BaseEventProperties.onConflict


optional overrideDates?: OverrideDatesMap

Force reschedule dates unconditionally. Unlike onConflict which handles conflicts, this always moves events. Key is the original computed date (YYYY-MM-DD), value is the new date.

overrideDates: {
"2026-02-18": "2026-02-20", // Move from Feb 18 to Feb 20
}

BaseEventProperties.overrideDates


optional priority?: number

Display precedence when several events land on the same day, like CSS z-index: higher = on top, default 0. The core only sorts by this number (highest first); it assigns no meaning to the values — the consumer does. Ties keep generation order (stable).

BaseEventProperties.priority


optional reminders?: Reminder[]

BaseEventProperties.reminders


optional source?: string

Origin of the event — the plugin, feed, or ICS subscription that produced it. Lets a consumer customize/filter in bulk by source (like toggling a calendar in Google/Apple Calendar) and namespaces the ICS export UID. Distinct from groupId (a user-defined group) and sourceEventId (the originating config id).

BaseEventProperties.source


optional startDate?: string

Recurrence validity window (YYYY-MM-DD, both bounds inclusive). Occurrences before startDate or after endDate are dropped — applied centrally during generation, so it works for ANY event type (const, monthly, weekly, nth-weekday, plugin types…), not just the few that ship their own range fields.

Maps iCalendar semantics: startDateDTSTART lower bound, endDateRRULE;UNTIL (which RFC 5545 defines as inclusive). Both are DATE values (all-day); recurrences are date-based, so no time component is involved.

// Weekly stand-up, but only for July 2026
{ type: "weekly", id: "standup", dayOfWeek: 1,
startDate: "2026-07-01", endDate: "2026-07-31" }

BaseEventProperties.startDate


optional startMonth?: number

Starting month for interval calculation (1-12, default: 1) Used with interval to determine which months the event occurs

1 // Start counting from January

optional startTime?: string

BaseEventProperties.startTime


optional status?: "confirmed" | "tentative" | "cancelled"

BaseEventProperties.status


optional templates?: Record<string, string>

Per-occurrence dynamic fields, derived from each occurrence’s date. A map of fieldName → template, where the template may contain date tokens ({YYYY} {MM} {DD} zero-padded · {M} {D} no padding). Each occurrence gets the field set to the interpolated value.

Applied during generation, after the base value and before a per-date exceptions[date].override (which always wins). Typically used for a date-specific url, but any string field works (title, description, location, …).

// Every Sunday's link points at a date page
{ type: "weekly", id: "mass", dayOfWeek: 0, title: "Mass",
templates: { url: "https://x.com/mass/{D}-{M}" } }
// 2026-07-07 → .../mass/7-7 · 2026-07-14 → .../mass/14-7

BaseEventProperties.templates


title: string

BaseEventProperties.title


type: "monthly"


optional url?: string

BaseEventProperties.url