Edge Function issues when using [email protected]

Update timeline

1. investigating Feb 05, 2026, 06:09 PM UTC

   Edge Functions using @supabase/[email protected] from esm.sh are failing. The issue is specific to the esm.sh CDN. Workarounds: Pin to v2.94.0 or use cdn.jsdelivr.net (https://cdn.jsdelivr.net/npm/@supabase/[email protected]/+esm) as a workaround while we investigate.

2. investigating Feb 05, 2026, 07:08 PM UTC

   We recommend importing via `npm:` or `jsr:` specifiers instead of CDN imports: `import { createClient } from "npm:@supabase/[email protected]"` These are more reliable than third-party CDNs. We’ve reached out to the esm.sh maintainer and are tracking the issue upstream.

3. identified Feb 05, 2026, 08:11 PM UTC

   We are removing v2.95.0 release, so the @2 tag will resolve to v2.94.1. This should resolve majority of issues. If you have previously switched to using v2.95.0 directly, please switch to v2.94.1

4. identified Feb 05, 2026, 09:36 PM UTC

   We’ve attempted several fixes on the npm registry side, but the esm.sh issue persists. We are continuing to investigate. In the meantime, use npm: or jsr: specifiers, or jsdelivr as an alternative CDN: import { createClient } from "npm:@supabase/[email protected]" or import { createClient } from "https://cdn.jsdelivr.net/npm/@supabase/[email protected]/+esm"

5. monitoring Feb 05, 2026, 11:53 PM UTC

   esm.sh maintainers have implemented a fix which should unblock deploys of Edge Functions that were importing supabase-js from esm.sh.

6. resolved Feb 06, 2026, 01:00 AM UTC

   Function deploys are working normally now. We are resolving this incident.