The Deno 2 migration removes the biggest friction point that held back Supabase Edge Functions adoption. Previously, using npm packages required awkward import map configurations and many popular libraries simply did not work. Now you can write "import Stripe from npm:stripe" and it resolves correctly. This means your existing Node.js utility code can move to edge functions with minimal changes.
Background tasks are the other headline feature. Before this update, edge functions had to complete all work before returning a response, which meant users waited while emails sent, webhooks fired, or analytics events processed. Now you can call a background task API that continues executing after the response is returned. The function stays alive for up to 60 seconds after the response, which is enough time for most async operations.
The performance improvements are notable too. Cold starts dropped from around 300ms to 180ms on average, and warm execution is consistently under 50ms for simple functions. Combined with Supabase's built-in Postgres integration, auth, and storage, edge functions are becoming a credible alternative to deploying a separate backend service. For small to medium projects, you can now build a complete backend using just Supabase without touching a VPS or container.
If you previously avoided Supabase Edge Functions due to npm compatibility issues, the Deno 2 upgrade fixes that - worth revisiting.
