Back to corpus
research notebacklog referencescore 24

Supabase Edge Functions

This skill provides operations for working with Supabase Edge Functions - serverless TypeScript/JavaScript functions that run on Deno Deploy. Use for invoking functions, deploying code, and managing function lifecycles.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

--- name: supabase-edge-functions description: Deploy and manage Supabase Edge Functions. Use for invoking serverless functions, deploying new functions, and managing function deployments. --- This skill provides operations for working with Supabase Edge Functions - serverless TypeScript/JavaScript functions that run on Deno Deploy. Use for invoking functions, deploying code, and managing function lifecycles. **Required tools:** - Supabase CLI (`supabase` command) - Deno (for local development) **Helper script:** This skill uses the shared Supabase API helper for invoking functions: | Status | Meaning | |--------|---------| | 200 | Success | | 400 | Bad request (invalid input) | | 401 | Unauthorized (invalid/missing auth) | | 403 | Forbidden (insufficient permissions) | | 500 | Internal server error (function crashed) | | 504 | Gateway timeout (function took too long) |

Promotion decision

What has to happen next

Keep in the searchable backlog until it intersects a live paper or system.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.