Skip to content

docs: add contributing guidance on where middleware belongs - #169

Open
mandarini wants to merge 1 commit into
mainfrom
docs/middleware-placement
Open

mandarini wants to merge 1 commit into
mainfrom
docs/middleware-placement

Conversation

@mandarini

@mandarini mandarini commented Sep 17, 2026

Copy link
Copy Markdown
Collaborator

Adds a "Contributing a middleware" section to CONTRIBUTING.md, with its table-of-contents entry. It states which middleware belong in this package (needs Supabase and works with zero configuration on Edge Functions, as the shipped entries do), sends middleware with no Supabase surface to its own package on top of @supabase/middleware, and documents the src/middleware/<name>/ layout with the three export wiring points and the README table row. It also records the naming rule: with* is middleware, terminal handlers take no prefix and live outside src/middleware/, and MCP-specific code stays separate. Tracked in SDK-1461; the engine side is supabase/middleware#42.

@mandarini
mandarini requested review from a team as code owners September 17, 2026 12:01
@mandarini mandarini assigned tomaspozo and unassigned tomaspozo Sep 17, 2026
@pkg-pr-new

pkg-pr-new Bot commented Sep 17, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@supabase/server@169

commit: de066f9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants