supabase-edge-functions

Supabase Edge Functions require explicit import strategies using npm: or jsr: prefixed packages, avoiding bare specifiers. Shared utilities should reside under supabase/functions/_shared using relative imports to minimize cross-dependencies and ensure consistent TypeScript deployments.

Deno Edge Functions handle safe background tasks using EdgeRuntime.waitUntil. This mechanism ensures processes complete securely without blocking the main execution thread, maintaining reliable runtime performance for background operations.

Supabase Edge Functions fail because file write operations are restricted to the /tmp directory. Enforcing explicit dependency versioning and relying on core Web APIs prevents runtime errors and ensures stable Deno execution.

Bare module specifiers are not supported in Supabase Edge Functions. You must use npm: or jsr: prefixed packages for imports, adopt a conservative dependency approach, and prefer core Web APIs and built-in functions over deno.land/x usage.

Multi-route handling in Supabase Edge Functions requires using Deno.serve and applying specific routing patterns. This approach organizes endpoints effectively within the Deno runtime while maintaining TypeScript type safety.

Yes, Deno.serve is enforced for creating Supabase Edge Functions. This requirement guarantees proper request handling within the Deno runtime, complementing environment variable practices and explicit dependency versioning for robust deployments.