@pgflow/edge-worker 0.0.0-fix-supa-version-d565b97a-20251124083521 → 0.0.0-fix-max-conn-2da7657d-20260112035120

package/README.md

@@ -63,20 +63,20 @@ import { Flow } from 'jsr:@pgflow/dsl/supabase';
 
 // Define a flow using Supabase preset for Supabase resources
 const AnalyzeWebsite = new Flow<{ url: string }>({
-  slug: 'analyze_website',
+  slug: 'analyzeWebsite',
 })
-  .step({ slug: 'fetch' }, async (input, context) => {
+  .step({ slug: 'fetch' }, async (flowInput, context) => {
     // Access Supabase resources through context
-    const response = await fetch(input.run.url, {
+    const response = await fetch(flowInput.url, {
       signal: context.shutdownSignal,
     });
     return { html: await response.text() };
   })
-  .step({ slug: 'save' }, async (input, context) => {
+  .step({ slug: 'save', dependsOn: ['fetch'] }, async (deps, context) => {
     // Use Supabase client from context
     const { data } = await context.supabase
       .from('websites')
-      .insert({ url: input.run.url, html: input.fetch.html })
+      .insert({ url: context.flowInput.url, html: deps.fetch.html })
       .select()
       .single();
     return data;
@@ -172,7 +172,7 @@ When defining flows that use Supabase resources, import `Flow` from the Supabase
 ```typescript
 import { Flow } from 'jsr:@pgflow/dsl/supabase';
 
-const MyFlow = new Flow<InputType>({ slug: 'my_flow' }).step(
+const MyFlow = new Flow<InputType>({ slug: 'myFlow' }).step(
   { slug: 'process' },
   async (input, context) => {
     // TypeScript knows context includes all Supabase resources
@@ -208,6 +208,16 @@ To run a manual test:
 1. Start Supabase: `pnpm nx supabase:start edge-worker`
 2. Follow the instructions in the specific test's README
 
+## Dependencies
+
+### PostgreSQL Client
+
+This package uses `jsr:@oscar6echo/postgres` - a JSR-compatible fork of the popular [postgres](https://github.com/porsager/postgres) package.
+
+**Why a fork?** The official `npm:postgres` package uses CommonJS exports (`export =`) which are incompatible with JSR's ES Module requirements. The npm version also fails to parse database URLs correctly in Supabase Edge Runtime, causing `CONNECT_TIMEOUT` errors. See [porsager/postgres#839](https://github.com/porsager/postgres/issues/839) for details.
+
+The fork is functionally identical to postgres v3.4.5, with only the export syntax changed for Deno/JSR compatibility.
+
 ## Building
 
 Run `nx build edge-worker` to build the library.

package/package.json

@@ -1,7 +1,12 @@
 {
   "name": "@pgflow/edge-worker",
-  "version": "0.0.0-fix-supa-version-d565b97a-20251124083521",
+  "version": "0.0.0-fix-max-conn-2da7657d-20260112035120",
   "license": "Apache-2.0",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/pgflow-dev/pgflow",
+    "directory": "pkgs/edge-worker"
+  },
   "type": "module",
   "main": "./dist/index.js",
   "module": "./dist/index.js",
@@ -15,6 +20,10 @@
     "./_internal": {
       "types": "./dist/_internal.d.ts",
       "import": "./dist/_internal.js"
+    },
+    "./testing": {
+      "types": "./dist/testing.d.ts",
+      "import": "./dist/testing.js"
     }
   },
   "files": [
@@ -29,8 +38,7 @@
   },
   "devDependencies": {
     "@types/deno": "^2.3.0",
-    "@types/node": "~18.16.20",
-    "supabase": "^2.50.3"
+    "@types/node": "~18.16.20"
   },
   "publishConfig": {
     "access": "public"