Is fetch handler pattern mandatory for adapters?

[kallebysantos]

@wobsoriano: Will this repo only accept runtimes that expose a fetch handler, or is there appetite for framework middleware adapters that don't follow the export default { fetch } pattern, specifically tanstack start which has middleware but no app.fetch equivalent? — Original question

[kallebysantos]

We initially defined the core primitives and our examples to work as export default { fetch } pattern.
Since its a common syntax for all modern runtime platforms like:

• Supabase Edge Functions,
• Cloudflare workers, Deno, Bun, Nodejs etc...

It doesn't mean that /adapters should strict follow export default { fetch } syntax, like the name says its an "adaptation" for a specific framework or platform.

So I believe that if Tanstack supports all serveless patterns that this package aims to be, it should be okay to not strict on the default syntax.

Any community member is welcome to implement an adapter, we just need to make sure it follows the best Dev Experiencie for the target framework its trying to fit.

[wobsoriano]

Amazing! I already have an idea for tanstack start and how it's going to be used:

Global — attaches Supabase clients to every request without requiring auth:

// src/start.ts
export const startInstance = createStart(() => ({
  requestMiddleware: [withSupabase({ allow: 'always' })],
}))

Per server function — layer stricter auth on top for protected calls:

// server/games.ts
export const getGames = createServerFn()
  middleware([withSupabase({ allow: 'user' })])
    .handler(async ({ context }) => {
      const { supabase } = context.supabaseContext
      return supabase.from('games').select()
  })

// components/GamesList.tsx
export function GamesList() {
  const fetchGames = useServerFn(getGames)
  // ..
}

Grouped routes — since requestMiddleware context flows into beforeLoad, protected route groups work without an extra server function:

// routes/_authed.tsx

export const Route = createFileRoute('/_authed')({
  beforeLoad: async ({ context }) => {
    if (!context.supabaseContext?.userClaims) {
       throw redirect({ to: '/login' })
    }
  }
})