Edge Function issues when using supabase-js@2.95.0

This incident has been resolved.

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

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/supabase-js@2.95.0" or import { createClient } from "https://cdn.jsdelivr.net/npm/@supabase/supabase-js@2.95.0/+esm"

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

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

Edge Functions using @supabase/supabase-js@2.95.0 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/supabase-js@2.95.0/+esm) as a workaround while we investigate.