You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tiny grammar followup
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
## Documentation
* Updated blog post with clearer explanations of Supabase Server
functionality and improved TypeScript usage examples.
* Enhanced environment variable guidance for local development and
platform configuration.
* Refined migration guidance with updated terminology and more
consistent phrasing throughout the post.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Copy file name to clipboardExpand all lines: apps/www/_blog/2026-05-06-introducing-supabase-server.mdx
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ This is a new package that handles auth verification, client setup, request cont
21
21
22
22
We anonymously analyzed 25,000 deployed Edge Functions and saw the same pattern everywhere: developers were rebuilding the same setup code over and over just to get to their actual business logic.
23
23
24
-
Every Supabase Edge Function starts the same way:
24
+
Most functions needed to:
25
25
26
26
- Create a Supabase client with `SUPABASE_ANON_KEY`
27
27
- Create another admin client with `SUPABASE_SERVICE_ROLE_KEY` that can bypass Row Level Security
@@ -31,7 +31,7 @@ Every Supabase Edge Function starts the same way:
31
31
- Wire up auth context
32
32
- Copy/paste the same `_shared/*.ts` files between functions
33
33
34
-
With `@supabase/server` just declare who can call your endpoint, and you get a fully initialized context back:
34
+
With `@supabase/server`you just declare who can call your endpoint and get a fully initialized context back:
35
35
36
36
- User-scoped Supabase client
37
37
- Admin client with service role access
@@ -288,7 +288,7 @@ If you would like to adopt the DX that this package provides, check our [SSR fra
288
288
289
289
**Does this only support Hono?**
290
290
291
-
No. `withSupabase` works with any runtime that supports the standard `Request`/`Response` Web API: Edge Functions, Cloudflare Workers, Bun, and more. Hono was the first framework adapter we shipped, and we have already merged a community PR for the H3 adapter. We expect to accept more through our community contributions to adapters.
291
+
No. `withSupabase` works with any runtime that supports the standard `Request`/`Response` Web API: Edge Functions, Cloudflare Workers, Bun, and more. Hono was the first framework adapter we shipped, and we have already merged a community PR for the H3 adapter. We expect to accept more community-contributed adapters.
292
292
293
293
**Where is the documentation?**
294
294
@@ -298,7 +298,7 @@ The package ships with full documentation in the [GitHub repo](https://github.co
298
298
299
299
On the Supabase platform and Local Development (CLI), your Edge Functions will receive the required environment variables to work out of the box (`SUPABASE_PUBLISHABLE_KEYS`, `SUPABASE_SECRET_KEYS`, `SUPABASE_JWKS`).
300
300
301
-
On local development or self-hosted environments, use the same plural form: `SUPABASE_PUBLISHABLE_KEYS` instead of `SUPABASE_ANON_KEY`, `SUPABASE_SECRET_KEYS` instead of `SUPABASE_SERVICE_ROLE_KEY`.
301
+
In local development or self-hosted environments, use the same plural form: `SUPABASE_PUBLISHABLE_KEYS` instead of `SUPABASE_ANON_KEY`, `SUPABASE_SECRET_KEYS` instead of `SUPABASE_SERVICE_ROLE_KEY`.
302
302
303
303
Check out the [environment variables documentation](https://github.com/supabase/server/blob/main/docs/environment-variables.md) for more details.
The skill gives Claude Code and Cursor full context on the API surface, patterns, and migration paths. From there, you can prompt your way through most tasks.
318
+
The skill gives Claude Code and Cursor full context about the API surface, patterns, and migration paths. From there, you can prompt your way through most tasks.
319
319
320
320
Migrate existing Edge Functions to the new API keys:
321
321
322
322
```
323
-
Analyze all edge functions, and plan a full migration to use
323
+
Analyze all Edge Functions, and plan a full migration to use
324
324
the new API keys with @supabase/server
325
325
```
326
326
@@ -334,7 +334,7 @@ endpoints for a todos table, using per-route auth
334
334
Add a protected Edge Function with admin operations:
335
335
336
336
```
337
-
Create an edge function that accepts user or secret key auth,
337
+
Create an Edge Function that accepts user or secret key auth,
338
338
reads from a user's profile with RLS, and writes audit logs
0 commit comments