@molecule/api-scheduler-cloudflare 1.0.2

package/LICENSE

@@ -0,0 +1,115 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work.
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship.
+
+      "Contribution" shall mean any work of authorship, including the
+      original version of the Work and any modifications or additions
+      to that Work, that is intentionally submitted to the Licensor for
+      inclusion in the Work by the copyright owner or by an individual or
+      Legal Entity authorized to submit on behalf of the copyright owner.
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by the Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      patent license to make, have made, use, offer to sell, sell, import,
+      and otherwise transfer the Work.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file.
+
+   5. Submission of Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND.
+
+   8. Limitation of Liability. In no event and under no legal theory shall
+      any Contributor be liable to You for damages.
+
+   9. Accepting Warranty or Additional Liability.
+
+   Copyright 2026 Molecule Dev, Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,169 @@
+<!--
+AUTO-GENERATED — DO NOT EDIT THIS FILE.
+Generated by `mlcl sync-docs` from the package's src/index.ts JSDoc + mlcl/registry.json.
+Edits here are overwritten on the next commit (molecule's pre-commit hook regenerates).
+To change this document, edit the module-level JSDoc in src/index.ts.
+Generated: 2026-08-06T03:42:48.089Z
+-->
+
+# @molecule/api-scheduler-cloudflare
+
+> **Auto-generated, AI-first package reference** for the [molecule.dev](https://molecule.dev) ecosystem.
+> It is written to be read by coding agents as much as by people, and is generated from this
+> package's source — edit `src/index.ts` JSDoc, not this file.
+
+`@molecule/api-scheduler-cloudflare` — a `@molecule/api-scheduler` provider
+for Cloudflare Workers, where **the platform owns the clock**.
+
+`@molecule/api-scheduler-default` keeps tasks running with `setInterval`,
+which needs a long-lived process. A Worker has none: it is an isolate that
+exists for one invocation. So this provider registers tasks and runs them
+when a **Cron Trigger** fires, via `runDueTasks()` from the Worker's
+`scheduled()` handler. The application code that calls `schedule()` does not
+change — only the bond wired in `bonds/`.
+
+## Quick Start
+
+```typescript
+import { schedule, setProvider, start } from '@molecule/api-scheduler'
+import { createProvider } from '@molecule/api-scheduler-cloudflare'
+
+const scheduler = createProvider()
+setProvider(scheduler)
+
+schedule({
+  name: 'monitor-sweep',
+  intervalMs: 60000,
+  async handler() {
+    // ...
+  },
+})
+
+// REQUIRED, same as the default provider: nothing runs until start().
+// Unlike it, start() begins no timers — a Worker has no process to hold one.
+start()
+
+// Then, from the Worker's scheduled() handler, wrapped in ctx.waitUntil():
+//   export default { async scheduled(event, env, ctx) {
+//     ctx.waitUntil(scheduler.runDueTasks())
+//   } }
+// and in wrangler.toml:  [triggers] crons = ["* * * * *"]
+void scheduler.runDueTasks()
+```
+
+## Type
+
+`provider`
+
+## Installation
+
+```bash
+npm install @molecule/api-scheduler-cloudflare @molecule/api-bond @molecule/api-scheduler
+```
+
+## API
+
+### Interfaces
+
+#### `CloudflareScheduler`
+
+A scheduler provider whose tasks are driven by Cloudflare Cron Triggers
+rather than by an in-process timer.
+
+`start()` and `stop()` gate whether {@link CloudflareScheduler.runDueTasks}
+will execute anything; they start no timers, because a Worker has no
+long-lived process to hold one. Nothing runs until the Worker's `scheduled()`
+handler calls `runDueTasks()`.
+
+```typescript
+interface CloudflareScheduler extends SchedulerProvider {
+  /**
+   * Run the scheduled tasks. Call this from the Worker's `scheduled()` handler.
+   *
+   * Tasks run SEQUENTIALLY and every rejection is captured, so one failing task
+   * can neither abort the sweep nor reject the caller's promise — a Cron
+   * Trigger invocation that throws is retried by the platform, which would
+   * re-run the tasks that had already succeeded.
+   *
+   * @returns The status of every task after the run.
+   */
+  runDueTasks(): Promise<TaskStatus[]>
+}
+```
+
+#### `CloudflareSchedulerOptions`
+
+Options for the Cloudflare Workers scheduler provider.
+
+```typescript
+interface CloudflareSchedulerOptions {
+  /**
+   * Honour each task's `intervalMs` as a floor, using an in-isolate record of
+   * when it last ran.
+   *
+   * Defaults to `false`, and false is almost always what you want. A Worker
+   * isolate is short-lived and there may be many of them, so "when did this last
+   * run" is NOT reliably known — a task skipped on that basis may simply never
+   * run. With the default, every Cron Trigger runs every enabled task and the
+   * trigger schedule IS the schedule, which is the only interpretation the
+   * platform can actually guarantee.
+   *
+   * Set this to `true` only when a duplicate run is more expensive than a missed
+   * one, and even then treat it as best-effort.
+   */
+  respectIntervalWithinIsolate?: boolean
+}
+```
+
+### Functions
+
+#### `createProvider(options)`
+
+Creates a Cloudflare Workers scheduler provider.
+
+```typescript
+function createProvider(options?: CloudflareSchedulerOptions): CloudflareScheduler
+```
+
+- `options` — Configuration options.
+
+**Returns:** A SchedulerProvider driven by Cron Triggers.
+
+## Core Interface
+
+Implements `@molecule/api-scheduler` interface.
+
+## Injection Notes
+
+### Requirements
+
+Peer dependencies:
+
+- `@molecule/api-scheduler` ^1.0.1
+- `@molecule/api-bond` ^1.0.1
+
+### Runtime Dependencies
+
+- `@molecule/api-bond`
+- `@molecule/api-scheduler`
+
+- **`intervalMs` is not honoured by default, and that is deliberate.** The
+  Cron Trigger cadence is the real schedule. A Worker isolate is short-lived
+  and there may be many, so "when did this task last run" is not reliably
+  known in-process; skipping a task on that basis can mean it never runs.
+  Set the interval you want in `wrangler.toml`, not in `intervalMs`. The
+  `respectIntervalWithinIsolate` option exists for the case where a duplicate
+  run costs more than a missed one, and even then it is best-effort.
+- **Nothing runs until `start()` is called**, exactly as with the default
+  provider. `runDueTasks()` on a stopped scheduler logs a warning and returns
+  an empty array rather than silently doing nothing — a Cron Trigger firing
+  into a stopped scheduler otherwise looks identical to having no work.
+- **`TaskStatus.nextRunAt` is always `null`.** Only the platform knows when
+  the next trigger fires, and this code cannot read the cron expression.
+  Computing a plausible-looking time would be a guess presented as a fact.
+- **Status counters live in the isolate and do not persist.** They are useful
+  for the current invocation, not as a run history — persist to D1/KV if you
+  need that.
+- **Wrap `runDueTasks()` in `ctx.waitUntil()`** so the invocation is not
+  cut short. The scheduled handler has a 15-minute budget; a sweep that
+  exceeds it is killed mid-task.

package/dist/index.d.ts

@@ -0,0 +1,69 @@
+/**
+ * `@molecule/api-scheduler-cloudflare` — a `@molecule/api-scheduler` provider
+ * for Cloudflare Workers, where **the platform owns the clock**.
+ *
+ * `@molecule/api-scheduler-default` keeps tasks running with `setInterval`,
+ * which needs a long-lived process. A Worker has none: it is an isolate that
+ * exists for one invocation. So this provider registers tasks and runs them
+ * when a **Cron Trigger** fires, via `runDueTasks()` from the Worker's
+ * `scheduled()` handler. The application code that calls `schedule()` does not
+ * change — only the bond wired in `bonds/`.
+ *
+ * @example
+ * ```ts
+ * // bonds/scheduler-cloudflare.ts
+ * import { bond } from '@molecule/api-bond'
+ * import { createProvider } from '@molecule/api-scheduler-cloudflare'
+ *
+ * export const scheduler = createProvider()
+ * export function setupSchedulerCloudflare(): void {
+ *   bond('scheduler', scheduler)
+ * }
+ * ```
+ *
+ * ```ts
+ * // worker.ts — the Cron Trigger entry point
+ * import { scheduler } from './bonds/scheduler-cloudflare.js'
+ * import { setupBonds } from './bonds/index.js'
+ *
+ * export default {
+ *   async scheduled(_event, _env, ctx) {
+ *     await setupBonds()          // registers tasks via schedule() + start()
+ *     ctx.waitUntil(scheduler.runDueTasks())
+ *   },
+ * }
+ * ```
+ *
+ * ```toml
+ * # wrangler.toml
+ * [triggers]
+ * crons = ["*/1 * * * *"]   # the trigger schedule IS the schedule
+ * ```
+ *
+ * @remarks
+ * - **`intervalMs` is not honoured by default, and that is deliberate.** The
+ *   Cron Trigger cadence is the real schedule. A Worker isolate is short-lived
+ *   and there may be many, so "when did this task last run" is not reliably
+ *   known in-process; skipping a task on that basis can mean it never runs.
+ *   Set the interval you want in `wrangler.toml`, not in `intervalMs`. The
+ *   `respectIntervalWithinIsolate` option exists for the case where a duplicate
+ *   run costs more than a missed one, and even then it is best-effort.
+ * - **Nothing runs until `start()` is called**, exactly as with the default
+ *   provider. `runDueTasks()` on a stopped scheduler logs a warning and returns
+ *   an empty array rather than silently doing nothing — a Cron Trigger firing
+ *   into a stopped scheduler otherwise looks identical to having no work.
+ * - **`TaskStatus.nextRunAt` is always `null`.** Only the platform knows when
+ *   the next trigger fires, and this code cannot read the cron expression.
+ *   Computing a plausible-looking time would be a guess presented as a fact.
+ * - **Status counters live in the isolate and do not persist.** They are useful
+ *   for the current invocation, not as a run history — persist to D1/KV if you
+ *   need that.
+ * - **Wrap `runDueTasks()` in `ctx.waitUntil()`** so the invocation is not
+ *   cut short. The scheduled handler has a 15-minute budget; a sweep that
+ *   exceeds it is killed mid-task.
+ *
+ * @module
+ */
+export * from './provider.js';
+export * from './types.js';
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiEG;AAEH,cAAc,eAAe,CAAA;AAC7B,cAAc,YAAY,CAAA"}

package/dist/index.js

@@ -0,0 +1,68 @@
+/**
+ * `@molecule/api-scheduler-cloudflare` — a `@molecule/api-scheduler` provider
+ * for Cloudflare Workers, where **the platform owns the clock**.
+ *
+ * `@molecule/api-scheduler-default` keeps tasks running with `setInterval`,
+ * which needs a long-lived process. A Worker has none: it is an isolate that
+ * exists for one invocation. So this provider registers tasks and runs them
+ * when a **Cron Trigger** fires, via `runDueTasks()` from the Worker's
+ * `scheduled()` handler. The application code that calls `schedule()` does not
+ * change — only the bond wired in `bonds/`.
+ *
+ * @example
+ * ```ts
+ * // bonds/scheduler-cloudflare.ts
+ * import { bond } from '@molecule/api-bond'
+ * import { createProvider } from '@molecule/api-scheduler-cloudflare'
+ *
+ * export const scheduler = createProvider()
+ * export function setupSchedulerCloudflare(): void {
+ *   bond('scheduler', scheduler)
+ * }
+ * ```
+ *
+ * ```ts
+ * // worker.ts — the Cron Trigger entry point
+ * import { scheduler } from './bonds/scheduler-cloudflare.js'
+ * import { setupBonds } from './bonds/index.js'
+ *
+ * export default {
+ *   async scheduled(_event, _env, ctx) {
+ *     await setupBonds()          // registers tasks via schedule() + start()
+ *     ctx.waitUntil(scheduler.runDueTasks())
+ *   },
+ * }
+ * ```
+ *
+ * ```toml
+ * # wrangler.toml
+ * [triggers]
+ * crons = ["*/1 * * * *"]   # the trigger schedule IS the schedule
+ * ```
+ *
+ * @remarks
+ * - **`intervalMs` is not honoured by default, and that is deliberate.** The
+ *   Cron Trigger cadence is the real schedule. A Worker isolate is short-lived
+ *   and there may be many, so "when did this task last run" is not reliably
+ *   known in-process; skipping a task on that basis can mean it never runs.
+ *   Set the interval you want in `wrangler.toml`, not in `intervalMs`. The
+ *   `respectIntervalWithinIsolate` option exists for the case where a duplicate
+ *   run costs more than a missed one, and even then it is best-effort.
+ * - **Nothing runs until `start()` is called**, exactly as with the default
+ *   provider. `runDueTasks()` on a stopped scheduler logs a warning and returns
+ *   an empty array rather than silently doing nothing — a Cron Trigger firing
+ *   into a stopped scheduler otherwise looks identical to having no work.
+ * - **`TaskStatus.nextRunAt` is always `null`.** Only the platform knows when
+ *   the next trigger fires, and this code cannot read the cron expression.
+ *   Computing a plausible-looking time would be a guess presented as a fact.
+ * - **Status counters live in the isolate and do not persist.** They are useful
+ *   for the current invocation, not as a run history — persist to D1/KV if you
+ *   need that.
+ * - **Wrap `runDueTasks()` in `ctx.waitUntil()`** so the invocation is not
+ *   cut short. The scheduled handler has a 15-minute budget; a sweep that
+ *   exceeds it is killed mid-task.
+ *
+ * @module
+ */
+export * from './provider.js';
+export * from './types.js';

package/dist/provider.d.ts

@@ -0,0 +1,37 @@
+/**
+ * Cloudflare Workers scheduler provider — the platform owns the clock.
+ *
+ * @module
+ */
+import type { SchedulerProvider, TaskStatus } from '@molecule/api-scheduler';
+import type { CloudflareSchedulerOptions } from './types.js';
+/**
+ * A scheduler provider whose tasks are driven by Cloudflare Cron Triggers
+ * rather than by an in-process timer.
+ *
+ * `start()` and `stop()` gate whether {@link CloudflareScheduler.runDueTasks}
+ * will execute anything; they start no timers, because a Worker has no
+ * long-lived process to hold one. Nothing runs until the Worker's `scheduled()`
+ * handler calls `runDueTasks()`.
+ */
+export interface CloudflareScheduler extends SchedulerProvider {
+    /**
+     * Run the scheduled tasks. Call this from the Worker's `scheduled()` handler.
+     *
+     * Tasks run SEQUENTIALLY and every rejection is captured, so one failing task
+     * can neither abort the sweep nor reject the caller's promise — a Cron
+     * Trigger invocation that throws is retried by the platform, which would
+     * re-run the tasks that had already succeeded.
+     *
+     * @returns The status of every task after the run.
+     */
+    runDueTasks(): Promise<TaskStatus[]>;
+}
+/**
+ * Creates a Cloudflare Workers scheduler provider.
+ *
+ * @param options - Configuration options.
+ * @returns A SchedulerProvider driven by Cron Triggers.
+ */
+export declare const createProvider: (options?: CloudflareSchedulerOptions) => CloudflareScheduler;
+//# sourceMappingURL=provider.d.ts.map

package/dist/provider.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"provider.d.ts","sourceRoot":"","sources":["../src/provider.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAGH,OAAO,KAAK,EAAiB,iBAAiB,EAAE,UAAU,EAAE,MAAM,yBAAyB,CAAA;AAE3F,OAAO,KAAK,EAAE,0BAA0B,EAAE,MAAM,YAAY,CAAA;AAa5D;;;;;;;;GAQG;AACH,MAAM,WAAW,mBAAoB,SAAQ,iBAAiB;IAC5D;;;;;;;;;OASG;IACH,WAAW,IAAI,OAAO,CAAC,UAAU,EAAE,CAAC,CAAA;CACrC;AAED;;;;;GAKG;AACH,eAAO,MAAM,cAAc,GAAI,UAAU,0BAA0B,KAAG,mBAkGrE,CAAA"}

package/dist/provider.js

@@ -0,0 +1,106 @@
+/**
+ * Cloudflare Workers scheduler provider — the platform owns the clock.
+ *
+ * @module
+ */
+import { getLogger } from '@molecule/api-bond';
+/**
+ * Creates a Cloudflare Workers scheduler provider.
+ *
+ * @param options - Configuration options.
+ * @returns A SchedulerProvider driven by Cron Triggers.
+ */
+export const createProvider = (options) => {
+    const respectInterval = options?.respectIntervalWithinIsolate ?? false;
+    const tasks = new Map();
+    const logger = getLogger();
+    let started = false;
+    const toStatus = (entry) => ({
+        name: entry.task.name,
+        lastRunAt: entry.lastRunAt,
+        // The platform decides when the next run happens, and this code cannot read
+        // the Worker's cron expression. Reporting a computed time would be a guess
+        // presented as fact, so this is null by design.
+        nextRunAt: null,
+        isRunning: entry.isRunning,
+        lastError: entry.lastError,
+        durationMs: entry.durationMs,
+        totalRuns: entry.totalRuns,
+        totalFailures: entry.totalFailures,
+        lastSuccessAt: entry.lastSuccessAt,
+        enabled: entry.task.enabled !== false,
+    });
+    const runTask = async (entry) => {
+        if (entry.isRunning) {
+            logger.warn(`Scheduler task '${entry.task.name}' skipped: previous execution still running`);
+            return;
+        }
+        entry.isRunning = true;
+        const startTime = Date.now();
+        try {
+            await entry.task.handler();
+            entry.lastError = null;
+            entry.lastSuccessAt = new Date().toISOString();
+        }
+        catch (error) {
+            entry.lastError = error instanceof Error ? error.message : String(error);
+            logger.error(`Scheduler task '${entry.task.name}' failed: ${entry.lastError}`);
+            entry.totalFailures++;
+        }
+        finally {
+            entry.isRunning = false;
+            entry.durationMs = Date.now() - startTime;
+            entry.totalRuns++;
+            entry.lastRunAt = new Date().toISOString();
+        }
+    };
+    return {
+        schedule(task) {
+            tasks.set(task.name, {
+                task,
+                lastRunAt: null,
+                isRunning: false,
+                lastError: null,
+                durationMs: null,
+                totalRuns: 0,
+                totalFailures: 0,
+                lastSuccessAt: null,
+            });
+        },
+        unschedule(name) {
+            return tasks.delete(name);
+        },
+        getStatus(name) {
+            const entry = tasks.get(name);
+            return entry ? toStatus(entry) : null;
+        },
+        getAllStatuses() {
+            return [...tasks.values()].map(toStatus);
+        },
+        start() {
+            started = true;
+        },
+        stop() {
+            started = false;
+        },
+        async runDueTasks() {
+            if (!started) {
+                // Loud: a Cron Trigger that fires into a stopped scheduler does nothing,
+                // and silence here looks identical to "there was no work to do".
+                logger.warn('Cloudflare scheduler: runDueTasks() called before start(); nothing ran');
+                return [];
+            }
+            const now = Date.now();
+            for (const entry of tasks.values()) {
+                if (entry.task.enabled === false)
+                    continue;
+                if (respectInterval && entry.lastRunAt) {
+                    if (now - new Date(entry.lastRunAt).getTime() < entry.task.intervalMs)
+                        continue;
+                }
+                await runTask(entry);
+            }
+            return [...tasks.values()].map(toStatus);
+        },
+    };
+};

package/dist/types.d.ts

@@ -0,0 +1,26 @@
+/**
+ * Type definitions for the Cloudflare Workers scheduler provider.
+ *
+ * @module
+ */
+/**
+ * Options for the Cloudflare Workers scheduler provider.
+ */
+export interface CloudflareSchedulerOptions {
+    /**
+     * Honour each task's `intervalMs` as a floor, using an in-isolate record of
+     * when it last ran.
+     *
+     * Defaults to `false`, and false is almost always what you want. A Worker
+     * isolate is short-lived and there may be many of them, so "when did this last
+     * run" is NOT reliably known — a task skipped on that basis may simply never
+     * run. With the default, every Cron Trigger runs every enabled task and the
+     * trigger schedule IS the schedule, which is the only interpretation the
+     * platform can actually guarantee.
+     *
+     * Set this to `true` only when a duplicate run is more expensive than a missed
+     * one, and even then treat it as best-effort.
+     */
+    respectIntervalWithinIsolate?: boolean;
+}
+//# sourceMappingURL=types.d.ts.map

package/dist/types.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"types.d.ts","sourceRoot":"","sources":["../src/types.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;GAEG;AACH,MAAM,WAAW,0BAA0B;IACzC;;;;;;;;;;;;;OAaG;IACH,4BAA4B,CAAC,EAAE,OAAO,CAAA;CACvC"}

package/dist/types.js

@@ -0,0 +1,6 @@
+/**
+ * Type definitions for the Cloudflare Workers scheduler provider.
+ *
+ * @module
+ */
+export {};

package/package.json

@@ -0,0 +1,45 @@
+{
+  "name": "@molecule/api-scheduler-cloudflare",
+  "version": "1.0.2",
+  "description": "Scheduler provider for Cloudflare Workers Cron Triggers — the platform owns the clock, so tasks run from the scheduled() handler instead of an in-process timer.",
+  "type": "module",
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "scripts": {
+    "build": "tsc",
+    "test": "vitest run",
+    "test:watch": "vitest"
+  },
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    }
+  },
+  "files": [
+    "dist",
+    "README.md"
+  ],
+  "keywords": [
+    "molecule",
+    "scheduler",
+    "cloudflare"
+  ],
+  "license": "Apache-2.0",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/molecule-dev/molecule.git",
+    "directory": "packages/api/bonds/scheduler/cloudflare"
+  },
+  "devDependencies": {
+    "@molecule/api-bond": "1.0.1",
+    "@molecule/api-scheduler": "1.0.1",
+    "@types/node": "26.1.2",
+    "typescript": "6.0.3",
+    "vitest": "4.1.10"
+  },
+  "peerDependencies": {
+    "@molecule/api-scheduler": "^1.0.1",
+    "@molecule/api-bond": "^1.0.1"
+  }
+}