Fix: Resolve Supabase Edge Function deployment timeout by updating import paths #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Supabase Edge Function deployment was failing due to timeout issues caused by the way dependencies were being imported directly from URLs (
esm.shanddeno.land).Solution
Updated the import strategy in
scout-cronfunctions to use the Deno import map (deno.json) instead of inline URL imports:@supabase/supabase-jsto usenpm:specifier in import mapstd/http/serverto use import map alias instead of direct URLChanges
@supabase/supabase-jsandstd/http/serverBenefits
deno.json