Deno.land is down, which means Supabase functions are down locally

@doganugurlu Looks like Deno team implemented a fix <a href="https:&#x2F;&#x2F;denostatus.com&#x2F;cllm0jzq219036bjottk03k2ac" rel="nofollow noreferrer">https:&#x2F;&#x2F;denostatus.com&#x2F;cllm0jzq219036bjottk03k2ac</a> Are you still experiencing the issue?<p>We used to cache the modules locally, I will need to check if we made any configuration change. Can you kindly open an issue for Supabase CLI - <a href="https:&#x2F;&#x2F;github.com&#x2F;supabase&#x2F;cli&#x2F;issues">https:&#x2F;&#x2F;github.com&#x2F;supabase&#x2F;cli&#x2F;issues</a>

It was a little shocking to see the Supabase CLI talking about downloading imports <i>every time</i> we started Supabase Functions, but I had assumed it was locally cached and maybe it was doing cache validation but logging to the console as &quot;Downloading.&quot; Well, turns out it was really downloading because now Supabase CLI failing with the 500 that the deno.land shows.<p>The issue talks about compilation failing as a result of the same live URL dependency.