Unable to deploy edge function (with axios) after upgrading the CLI

[muezz]

Describe the bug I upgraded Supabase CLI on my machine to the latest version and it does not allow me to deploy my edge function. This goes away if I remove axios as a dependancy.

To Reproduce Steps to reproduce the behavior:

1. Create a new edge function
2. Import axios from https://esm.sh/axios@1.6.7. I use import map but I doubt that has an effect here.
3. Try deploying with supabase functions deploy my-func --no-verify-jwt
4. See error

Expected behavior The edge function should deploy without any errors which it does if I remove the axios dependancy.

System information Rerun the failing command with --create-ticket flag.

• Ticket ID: 86d01ebc550c4f12ba808a63efbe4307
• Version of OS: macOS Sonoma 14.4
• Version of CLI: v1.148.6
• Version of Docker: v24.0.6
• Versions of services: SERVICE IMAGE │ LOCAL │ LINKED supabase/postgres │ 15.1.0.147 │ 15.1.0.12 supabase/gotrue │ v2.143.0 │ v2.143.0 postgrest/postgrest │ v12.0.1 │ v10.2.0 supabase/realtime │ v2.25.66 │ - supabase/storage-api │ v0.46.4 │ v0.48.2 supabase/edge-runtime │ v1.38.0 │ - supabase/studio │ 20240301-0942bfe │ - supabase/postgres-meta │ v0.79.0 │ - supabase/logflare │ 1.4.0 │ - bitnami/pgbouncer │ 1.20.1-debian-11-r39 │ - darthsim/imgproxy │ v3.8.0 │ -

[laktek]

@muezz I think if you use esm.sh's axios you need to also import the xhr as a polyfill. Try adding this import to the top of your function's source file.

import "https://deno.land/x/xhr@0.1.0/mod.ts";

You can try directly importing axios from npm: ie. import axios from "npm:axios@1.6.7"

That should work without needing any polyfills.

[muezz]

@laktek I actually ended up removing axios as a dependancy as I was in a hurry to deploy the functions. I will try it out when I need to use axios again.

If this is indeed not a bug and something that you have to do (I mean importing xhr), let me know and I will close this ticket.

[laktek]

yeah, our recommendation would be to use npm:axios if you need to use it.

I will close this issue since there's no fix needed from our end.