Prisma 8 + Supabase: blog post and extension docs guide - #8131
Draft
ankur-arch wants to merge 21 commits into
Draft
ankur-arch wants to merge 21 commits into
ankur-arch wants to merge 21 commits into
Conversation
Blog: prisma-8-supabase-rls-and-auth (Will + Ankur), covering RLS policies in the Prisma contract and the supabase:auth.AuthUser cross-space FK, with hero/meta cover images. Docs: orm/next/extensions/supabase guide following the docs-writer conventions. All code executed against a real hosted Supabase project and deployed to Prisma Compute; see the test evidence in the PR description. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueComment |
Contributor
🍈 Lychee Link Check Report10 links: ✅ All links are working!Full Statistics Table
|
|
The latest updates on your projects. Learn more about Argos notifications ↗︎ Awaiting the start of a new Argos build… |
Blog: new benefit-led title, pain-first opening, schema and policy in the first third, one policy shown in full, before/after and request-flow diagrams, Compute/versions/test-report sections cut. Docs: replace unsupported 'terminal' code fence language with 'bash' (broke the Shiki-based docs build and every downstream docs check) and add the new page's SQL catalog terms plus PostgREST to cspell. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ankur-arch
commented
Aug 6, 2026
Pyramid-principle pass: RC1 framing throughout with a feedback CTA, sections renamed to reader takeaways, connected prose instead of fragments, proof section removed, limitations reframed around supported scenarios. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Restructure in the Turborepo-guide style: what-you'll-learn list, connection details collected up front, numbered steps with expected output after each command, plain-language explanations of the auth relation, @@rls, and policy blocks, and a verification step. RC1 framing replaces Early Access copy; jargon (contract space, facade, secondary root) replaced with plain terms. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Validated the full guide against a fresh hosted Supabase project on prisma@next (rc.6 CLI + rc.4 extension): scaffold, extension config, session pooler connection, contract emit, migration plan + migrate (policy hash names and auth.users FK match the published SQL), all six RLS behavior checks (owner-scoped select with no filter, zero-row cross-user update, WITH CHECK rejection of forged inserts, empty anon reads, service_role bypass), and the db verify storage.iceberg known issue with --marker-only as the workaround. Only divergence found: the extension snapshot lands in migrations/snapshots/ referenced from migrations/supabase/, and the app migration in migrations/app/, so the step-7 bullet now says to commit the whole migrations directory. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…one idea per paragraph Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KQCq52DbjW5rnYPEBTjaJv
…over; guide on db migrate - Blog: lead with the one-file authorization model, show three concrete supabase-js failure modes (service-role .eq, hand-written policy SQL, separate type generation), then the Prisma 8 answer with a live 7-check RLS run against a fresh Supabase project. - Commands moved to npx prisma@latest (8.0.0-rc.12): migrate -> db migrate, migration ref set db for follow-up plans. - Guide: same command updates, runnable src/check.ts, PLAN_ORIGIN_UNKNOWN troubleshooting, /orm/extensions paths after the main merge. - Cover regenerated in the 2026 brand: paper surface, prism cyan accent, prism mark + Supabase tiles, ink code card, full-color lockup sign-off. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KQCq52DbjW5rnYPEBTjaJv
…on rc.13 Blog: restructure value-first (what you get, schema legend, three commands, no-filter query, six-line check output), add "If you use supabase-js today" with three comparisons each citing verified Supabase GitHub issues, a side-by-side table, and name Edge Functions as staying on supabase-js. Link the RLS issue at its new prisma/orm URL. Guide: use `db migrate --advance-ref db` from the first migrate (it creates the db ref, so manual `ref set` is gone), extend the check script to six checks, drop the stale "npx prisma == npx prisma@latest" claim, add the column-before-policy drop-order gotcha to troubleshooting. Every command and output re-run against a fresh Supabase project on prisma@latest 8.0.0-rc.13 / extension rc.8. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y2EHLWBJnNdder935Hwaat
…he supabase-js comparison Cites the highest-reaction supabase-js and postgrest-js threads for each problem (client-side transactions, Json type depth, to-one join typing, insert types, timestamptz as Date, BigInt, throwOnError) and extends the side-by-side table. Style pass over the rest of the post: fewer contrast slogans and absolutes, split the semicolon-joined limitations sentence. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…ap, smooth prose The demo's Enforce step now renders the policy_select block from the schema (highlighted with the Prisma 8 grammar) instead of the CREATE POLICY SQL. The code column gets the wider grid share and scrolls long lines instead of overlapping the captions. Prose pass joins the short chopped sentences from the last revision into longer ones. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Resolves: extensions meta.json keeps main's new index page and adds supabase; docs package.json takes shiki from the catalog; lockfile regenerated from main. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
TL;DR
Adds the Prisma 8 + Supabase launch content: the blog post ("Your Supabase RLS policies and auth.users, in your Prisma contract", authors Will + Ankur, with cover images) and the
orm/next/extensions/supabasedocs guide. Every command and code block was executed against a real hosted Supabase project and deployed to Prisma Compute before being written down. Draft until launch coordination (publish date + public example repo link).What's in the PR
apps/blog/content/blog/prisma-8-supabase-rls-and-auth/index.mdx+hero.svg/meta.png(Eclipse house style, official Prisma + Supabase logos)apps/docs/content/docs/orm/next/extensions/supabase.mdx+ registration in the extensionsmeta.jsonEvidence behind the content
@@rls+ 4 policies,supabase:auth.AuthUserFK, Hono API) built withprisma-next@0.17.0,@prisma/orm-postgres@0.17.0,@prisma/orm-extension-supabase@0.17.0db verifyfails on current hosted projects due to extension storage-contract drift; workaround--marker-only)Conventions
prisma@nextdoes not exist)docs-writerskill (numbered steps, verify blocks, troubleshooting, agent prompt); one flagged deviation: the skill reference still says "Prisma Next", overridden by the Prisma 8 naming decisionBefore merge
TODO before publishcomment with the public example repo link🤖 Generated with Claude Code