Serverless route coverage is now broad enough to be useful for copy/paste evaluation:

• shipped docs: Cloudflare Worker, Hono, Deno Deploy, SvelteKit, Fastify, Express, Koa, AWS Lambda Function URL, and Bun.serve()
• runnable smoke path: examples/serverless-workpaper-api still verifies formula recalculation, persistence, restore, and JSON readback with "verified": true
• open first-timer adapter tasks: Netlify Functions docs(serverless): add Netlify Functions adapter #178, Hapi docs(serverless): add Hapi route adapter #179, Cloudflare Pages Functions docs(serverless): add Cloudflare Pages Functions adapter #180, Remix docs(serverless): add Remix resource route adapter #181, Nitro docs(serverless): add Nitro event handler adapter #182, NestJS docs(serverless): add NestJS controller adapter #183, Elysia docs(serverless): add Elysia route adapter #184, and Vercel Functions docs(serverless): add Vercel Function adapter #185

If you want a runtime covered, comment here with the framework and the request/response shape you need. The adapter should stay thin: build a web-standard Request, call handleWorkPaperRequest(), and copy the returned Response back into the framework.

May 13 update: I refreshed this into a smaller adapter backlog again, this time focused on runnable or copy-paste service proofs instead of broad framework coverage.

Current first-timer issues for this route family:

• Hono route smoke: docs(examples): add a runnable Hono WorkPaper route smoke #257
• Cloudflare KV persistence snippet: docs(examples): add Cloudflare KV WorkPaper persistence snippet #258
• Prisma-backed WorkPaper JSON persistence recipe: docs(service): add Prisma-backed WorkPaper JSON persistence recipe #259
• Fastify route smoke snippet: docs(examples): add Fastify WorkPaper route smoke snippet #260

The target is still the same: accept records, build a WorkPaper, calculate formulas, return computed JSON, and prove persistence/readback when state is involved.

If you are using spreadsheet logic behind an HTTP boundary, the useful feedback is concrete: which runtime would you actually copy first, and what payload/result shape would make the example worth trying? I am especially interested in whether durable workbook JSON belongs in KV/object storage, a database row, or should stay out of the first example entirely.

May 13 update: the Next.js App Router path is now runnable instead of just described in prose.

What changed:

• source: https://github.com/proompteng/bilig/blob/main/examples/serverless-workpaper-api/next-route-handler.ts
• command: npm run next-route-handler from examples/serverless-workpaper-api
• docs: https://proompteng.github.io/bilig/serverless-workpaper-api-route.html

The smoke exports runtime = "nodejs", dynamic = "force-dynamic", and GET() / POST() wrappers that delegate to the shared WorkPaper Request -> Response handler. It sends a summary read, posts revenue records, reads the summary again, and only prints verified: true after formula readback and serialized WorkPaper persistence both hold.

If you are using spreadsheet logic behind an API route, the next useful feedback is specific: would you copy this shape into Next.js as-is, or do you need the example to show Vercel storage, tRPC, Drizzle/Kysely persistence, or a different request/response boundary first?