@bobfrankston/mailx-store 0.1.20 → 0.1.22

package/db.d.ts

@@ -83,6 +83,7 @@ export declare class MailxDB {
         recurringEventId?: string;
         htmlLink?: string;
         isHoliday?: boolean;
+        reminderMinutes?: number[];
     }): string;
     getCalendarEvents(accountId: string, fromMs: number, toMs: number): any[];
     /** Lookup by uuid only — used by patch/delete paths that don't have an

package/db.js

@@ -411,6 +411,15 @@ export class MailxDB {
         // calendar_events table; the flag distinguishes them so the UI can
         // style them differently and the alarm scheduler can skip them.
         this.addColumnIfMissing("calendar_events", "is_holiday", "INTEGER NOT NULL DEFAULT 0");
+        // Per-event reminder offsets (Bob 2026-05-12: "use the reminder
+        // times in the event (there can be multiple)"). Google's API
+        // returns `reminders.overrides` as an array of {method, minutes}
+        // — we store the minute offsets as JSON so alarms.ts can fire ONE
+        // popup per offset (10-min, 30-min, 1-day, …) instead of the
+        // hard-coded 10-min default. `useDefault: true` events get the
+        // calendar's defaultReminders pre-resolved server-side and pulled
+        // through here too.
+        this.addColumnIfMissing("calendar_events", "reminder_minutes_json", "TEXT DEFAULT '[]'");
         // Backfill UUIDs for any pre-existing rows that were inserted before
         // this column landed. One UPDATE + an id roundtrip per row — cheap
         // at our row counts, runs once per DB upgrade.
@@ -733,12 +742,13 @@ export class MailxDB {
     // ── Calendar events (two-way cache) ──
     upsertCalendarEvent(ev) {
         const uuid = ev.uuid || randomUUID().replace(/-/g, "");
+        const remindersJson = JSON.stringify(Array.isArray(ev.reminderMinutes) ? ev.reminderMinutes : []);
         this.db.prepare(`
             INSERT INTO calendar_events
                 (uuid, account_id, provider_id, calendar_id, title, start_ms, end_ms,
                  all_day, location, notes, etag, last_synced, dirty, deleted, updated_at,
-                 recurring_event_id, html_link, is_holiday)
-            VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, 0, ?, ?, ?, ?)
+                 recurring_event_id, html_link, is_holiday, reminder_minutes_json)
+            VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, 0, ?, ?, ?, ?, ?)
             ON CONFLICT(uuid) DO UPDATE SET
                 account_id=excluded.account_id, provider_id=excluded.provider_id,
                 calendar_id=excluded.calendar_id, title=excluded.title,
@@ -749,8 +759,9 @@ export class MailxDB {
                 updated_at=excluded.updated_at,
                 recurring_event_id=excluded.recurring_event_id,
                 html_link=excluded.html_link,
-                is_holiday=excluded.is_holiday
-        `).run(uuid, ev.accountId, ev.providerId || null, ev.calendarId || "primary", ev.title, ev.startMs, ev.endMs, ev.allDay ? 1 : 0, ev.location || "", ev.notes || "", ev.etag || null, ev.dirty ? 0 : Date.now(), ev.dirty ? 1 : 0, Date.now(), ev.recurringEventId || null, ev.htmlLink || null, ev.isHoliday ? 1 : 0);
+                is_holiday=excluded.is_holiday,
+                reminder_minutes_json=excluded.reminder_minutes_json
+        `).run(uuid, ev.accountId, ev.providerId || null, ev.calendarId || "primary", ev.title, ev.startMs, ev.endMs, ev.allDay ? 1 : 0, ev.location || "", ev.notes || "", ev.etag || null, ev.dirty ? 0 : Date.now(), ev.dirty ? 1 : 0, Date.now(), ev.recurringEventId || null, ev.htmlLink || null, ev.isHoliday ? 1 : 0, remindersJson);
         return uuid;
     }
     getCalendarEvents(accountId, fromMs, toMs) {
@@ -778,7 +789,15 @@ export class MailxDB {
         return rows.map(this.calendarRowToObject);
     }
     calendarRowToObject(r) {
+        let reminderMinutes = [];
+        try {
+            const parsed = JSON.parse(r.reminder_minutes_json || "[]");
+            if (Array.isArray(parsed))
+                reminderMinutes = parsed.filter((n) => Number.isFinite(n)).map((n) => Number(n));
+        }
+        catch { /* invalid JSON → empty */ }
         return {
+            reminderMinutes,
             uuid: r.uuid, accountId: r.account_id, providerId: r.provider_id,
             calendarId: r.calendar_id, title: r.title, startMs: r.start_ms,
             endMs: r.end_ms, allDay: !!r.all_day, location: r.location, notes: r.notes,

package/index.d.ts

@@ -4,4 +4,5 @@
  */
 export { MailxDB } from "./db.js";
 export { FileMessageStore } from "./file-store.js";
+export { parseSerial } from "./parse-serial.js";
 //# sourceMappingURL=index.d.ts.map

package/index.js

@@ -4,4 +4,5 @@
  */
 export { MailxDB } from "./db.js";
 export { FileMessageStore } from "./file-store.js";
+export { parseSerial } from "./parse-serial.js";
 //# sourceMappingURL=index.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bobfrankston/mailx-store",
-  "version": "0.1.20",
+  "version": "0.1.22",
   "type": "module",
   "main": "index.js",
   "types": "index.d.ts",
@@ -10,7 +10,8 @@
   "license": "ISC",
   "dependencies": {
     "@bobfrankston/mailx-types": "^0.1.11",
-    "@bobfrankston/mailx-settings": "^0.1.16"
+    "@bobfrankston/mailx-settings": "^0.1.16",
+    "mailparser": "^3.7.2"
   },
   "repository": {
     "type": "git",
@@ -21,12 +22,14 @@
   },
   ".dependencies": {
     "@bobfrankston/mailx-types": "file:../mailx-types",
-    "@bobfrankston/mailx-settings": "file:../mailx-settings"
+    "@bobfrankston/mailx-settings": "file:../mailx-settings",
+    "mailparser": "^3.7.2"
   },
   ".transformedSnapshot": {
     "dependencies": {
       "@bobfrankston/mailx-types": "^0.1.11",
-      "@bobfrankston/mailx-settings": "^0.1.16"
+      "@bobfrankston/mailx-settings": "^0.1.16",
+      "mailparser": "^3.7.2"
     }
   }
 }

package/parse-serial.d.ts

@@ -0,0 +1,33 @@
+/**
+ * Process-wide serialized simpleParser.
+ *
+ * mailparser's `simpleParser` is declared `async` but its work is CPU-bound
+ * (Node Streams + libmime decoding). When N parses run concurrently on the
+ * single-threaded event loop they share CPU and each finishes at roughly
+ * N× wall-clock. Real evidence (2026-05-13): four near-concurrent parses
+ * each reported `14691ms for 3 KB` — pure contention, not size.
+ *
+ * The downstream symptom is the IPC pipe: while the event loop is
+ * saturated by interleaving parses, unrelated IPC operations (mark-as-spam,
+ * move, delete) wait their turn and the WebView-side `mailxapi` shim
+ * times out at 120s with a misleading "stayed in the list" alert.
+ *
+ * Serializing through a module-level promise chain bounds the damage with
+ * minimal plumbing: a single parse runs at full CPU and finishes in its
+ * natural ~50-500ms budget; the next parse starts when it's done. Each
+ * UI click produces a clean preview latency instead of a 14-second stall.
+ *
+ * Lives in mailx-store rather than mailx-service so both the UI-hot path
+ * (mailx-service/local-store.ts) and the sync path (mailx-imap) can share
+ * one queue — otherwise sync-time parses would still contend with UI
+ * parses through the event loop, just not through this module's chain.
+ *
+ * Future work: replace the in-process chain with a `node:worker_threads`
+ * pool. The chain is the precursor that bounds the worst case while the
+ * pool is built.
+ */
+import { type ParsedMail, type Source } from "mailparser";
+/** Serialized wrapper around `mailparser.simpleParser`. Drop-in replacement —
+ *  same signature, same return value. */
+export declare function parseSerial(source: Source): Promise<ParsedMail>;
+//# sourceMappingURL=parse-serial.d.ts.map

package/parse-serial.js

@@ -0,0 +1,38 @@
+/**
+ * Process-wide serialized simpleParser.
+ *
+ * mailparser's `simpleParser` is declared `async` but its work is CPU-bound
+ * (Node Streams + libmime decoding). When N parses run concurrently on the
+ * single-threaded event loop they share CPU and each finishes at roughly
+ * N× wall-clock. Real evidence (2026-05-13): four near-concurrent parses
+ * each reported `14691ms for 3 KB` — pure contention, not size.
+ *
+ * The downstream symptom is the IPC pipe: while the event loop is
+ * saturated by interleaving parses, unrelated IPC operations (mark-as-spam,
+ * move, delete) wait their turn and the WebView-side `mailxapi` shim
+ * times out at 120s with a misleading "stayed in the list" alert.
+ *
+ * Serializing through a module-level promise chain bounds the damage with
+ * minimal plumbing: a single parse runs at full CPU and finishes in its
+ * natural ~50-500ms budget; the next parse starts when it's done. Each
+ * UI click produces a clean preview latency instead of a 14-second stall.
+ *
+ * Lives in mailx-store rather than mailx-service so both the UI-hot path
+ * (mailx-service/local-store.ts) and the sync path (mailx-imap) can share
+ * one queue — otherwise sync-time parses would still contend with UI
+ * parses through the event loop, just not through this module's chain.
+ *
+ * Future work: replace the in-process chain with a `node:worker_threads`
+ * pool. The chain is the precursor that bounds the worst case while the
+ * pool is built.
+ */
+import { simpleParser } from "mailparser";
+let _chain = Promise.resolve();
+/** Serialized wrapper around `mailparser.simpleParser`. Drop-in replacement —
+ *  same signature, same return value. */
+export async function parseSerial(source) {
+    const queued = _chain.then(() => simpleParser(source));
+    _chain = queued.catch(() => undefined);
+    return queued;
+}
+//# sourceMappingURL=parse-serial.js.map