fix: replace npm:postgres with jsr:@oscar6echo/postgres for Supabase Edge Runtime compatibility (#552)

# Fix Supabase Edge Runtime compatibility with postgres client

This PR replaces `npm:postgres` with `jsr:@oscar6echo/postgres` fork to fix compatibility issues with Supabase Edge Runtime. The original npm package fails to parse database URLs in Deno edge environments, causing CONNECT_TIMEOUT errors.

## Changes:
- Replaced `npm:postgres@3.4.5` with `jsr:@oscar6echo/postgres@3.4.5-d` in all Deno configuration files
- Updated type imports from `Sql` to `postgres.Sql` throughout the codebase
- Added documentation in the README explaining why we're using a fork
- Removed deno.lock files which will be regenerated with the new dependency

The fork is functionally identical to postgres v3.4.5, with only the export syntax changed for Deno/JSR compatibility. This resolves the issue described in porsager/postgres#839.

Author: jumski

.changeset/jsr-postgres-fork.md

@@ -0,0 +1,7 @@
+---
+'@pgflow/edge-worker': patch
+'@pgflow/dsl': patch
+'pgflow': patch
+---
+
+Fix Supabase Edge Runtime compatibility by replacing npm:postgres with jsr:@oscar6echo/postgres fork. The npm package fails to parse database URLs in Deno edge environments, causing CONNECT_TIMEOUT errors.

apps/demo/supabase/functions/article_flow_worker/deno.json

@@ -8,7 +8,7 @@
 		"@pgflow/edge-worker": "../_vendor/@pgflow/edge-worker/index.ts",
 		"@pgflow/edge-worker/": "../_vendor/@pgflow/edge-worker/",
 		"@pgflow/edge-worker/_internal": "../_vendor/@pgflow/edge-worker/_internal.ts",
-		"postgres": "npm:postgres@3.4.5",
+		"postgres": "jsr:@oscar6echo/postgres@3.4.5-d",
 		"@henrygd/queue": "jsr:@henrygd/queue@^1.0.7",
 		"@supabase/supabase-js": "jsr:@supabase/supabase-js@^2.49.4"
 	}

apps/demo/supabase/functions/article_flow_worker/deno.lock

@@ -15,7 +15,7 @@
     "@pgflow/edge-worker/_internal": "../_vendor/@pgflow/edge-worker/_internal.ts",
     "@henrygd/queue": "jsr:@henrygd/queue@^1.0.7",
     "@supabase/supabase-js": "jsr:@supabase/supabase-js@^2.49.4",
-    "postgres": "npm:postgres@3.4.5",
+    "postgres": "jsr:@oscar6echo/postgres@3.4.5-d",
     "@std/crypto": "jsr:@std/crypto"
   }
 }

pkgs/cli/supabase/functions/pgflow/deno.json

@@ -1,4 +1,4 @@
-import type { Sql } from 'postgres';
+import type postgres from 'postgres';
 import type { SupabaseClient } from '@supabase/supabase-js';
 import {
   Flow as CoreFlow,
@@ -8,7 +8,7 @@ import {
 
 /* ---------- 1. Resources ------------------------------------------- */
 export interface SupabaseResources extends Record<string, unknown> {
-  sql            : Sql;
+  sql            : postgres.Sql;
   /**
    * Supabase client with service role key for full database access
    */

pkgs/dsl/src/platforms/supabase.ts

@@ -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.