@fedify/cfworkers 2.0.36-dev.2551 → 2.0.36-dev.2637

package/README.md

@@ -16,35 +16,44 @@ implementations for [Cloudflare Workers]:
  -  [`WorkersMessageQueue`]
 
 ~~~~ typescript
-import type { Federation } from "@fedify/fedify";
+import { createFederation, type Message } from "@fedify/fedify";
 import { WorkersKvStore, WorkersMessageQueue } from "@fedify/cfworkers";
 
+type Env = {
+  KV_BINDING: KVNamespace<string>;
+  QUEUE_BINDING: Queue;
+};
+
 export default {
-  async fetch(request, env, ctx) {
-    const federation = createFederation({
+  async fetch(request: Request, env: Env): Promise<Response> {
+    const federation = createFederation<Env>({
       kv: new WorkersKvStore(env.KV_BINDING),
       queue: new WorkersMessageQueue(env.QUEUE_BINDING),
+      // Cloudflare Queues cannot be polled, so the queue() handler below
+      // consumes the messages instead of Federation.startQueue():
+      manuallyStartQueue: true,
       // ... other options
     });
-    
-    return federation.handle(request, { contextData: env });
+
+    return await federation.fetch(request, { contextData: env });
   },
-  
-  async queue(batch, env, ctx) {
-    const federation = createFederation({
+
+  async queue(batch: MessageBatch<unknown>, env: Env): Promise<void> {
+    const federation = createFederation<Env>({
       kv: new WorkersKvStore(env.KV_BINDING),
       queue: new WorkersMessageQueue(env.QUEUE_BINDING),
+      // Inbox listeners run inside processQueuedTask() and may call
+      // ctx.sendActivity(), which would otherwise start the queue workers
+      // automatically:
+      manuallyStartQueue: true,
       // ... other options
     });
-    
+
     for (const message of batch.messages) {
-      await federation.processQueuedTask(message.body);
+      await federation.processQueuedTask(env, message.body as Message);
     }
-  }
-} satisfies ExportedHandler<{ 
-  KV_BINDING: KVNamespace<string>;
-  QUEUE_BINDING: Queue;
-}>;
+  },
+} satisfies ExportedHandler<Env>;
 ~~~~
 
 [JSR badge]: https://jsr.io/badges/@fedify/cfworkers
@@ -99,7 +108,9 @@ management.
 > API when new messages are available in the queue.  Inside the `queue()`
 > method, you need to call `Federation.processQueuedTask()` method to manually
 > process the messages.  The `queue()` method is the only way to consume
-> messages from the queue in Cloudflare Workers.
+> messages from the queue in Cloudflare Workers.  Set `manuallyStartQueue` to
+> `true` as well; otherwise Fedify tries to start the workers automatically,
+> and since `listen()` throws, it logs a warning that they could not be started.
 
 [Cloudflare Queues]: https://developers.cloudflare.com/queues/
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fedify/cfworkers",
-  "version": "2.0.36-dev.2551+8b012df4",
+  "version": "2.0.36-dev.2637+cc2cd6fb",
   "description": "Adapt Fedify with Cloudflare Workers",
   "keywords": [
     "Fedify",
@@ -52,7 +52,7 @@
   ],
   "peerDependencies": {
     "@cloudflare/workers-types": "^4.20250906.0 || ^5.0.0",
-    "@fedify/fedify": "^2.0.36-dev.2551+8b012df4"
+    "@fedify/fedify": "^2.0.36-dev.2637+cc2cd6fb"
   },
   "devDependencies": {
     "@cloudflare/vitest-pool-workers": "^0.8.31",