feat: add per-request store API (getRequestStore)

[JamesbbBriz]

Summary

Add getRequestStore() — a per-request key-value store backed by vinext's existing unified AsyncLocalStorage scope. Values are isolated per request and automatically garbage-collected when the request completes.

Primary use case: per-request database clients on Cloudflare Workers, where global singletons cause alternating request failures (#537).

API

import { getRequestStore } from "vinext/request-store";

export function getPrisma(connectionString: string): PrismaClient {
  const store = getRequestStore();
  let prisma = store.get("prisma") as PrismaClient | undefined;
  if (!prisma) {
    const pool = new Pool({ connectionString });
    prisma = new PrismaClient({ adapter: new PrismaPg(pool) });
    store.set("prisma", prisma);
  }
  return prisma;
  // Request ends → Map GC'd → connection released
}

Similar pattern to SvelteKit event.locals, Hono c.set/get, Remix context.

Scope

Works in all code paths:

Code path	Supported	Notes
App Router route handlers	✅	Already wrapped by RSC entry
App Router server components/actions	✅	Already wrapped by RSC entry
Pages Router API routes (dev)	✅	Wrapped in this PR (api-handler.ts)
Pages Router API routes (prod)	✅	Wrapped in this PR (pages-server-entry.ts)
Middleware	✅	Inherits ExecutionContext into unified scope
Outside request scope (tests, top-level)	⚠️	Returns fresh empty Map each call — safe but non-persistent

Changes

File	Change
shims/unified-request-context.ts	Add userStore: Map<string, unknown> to UnifiedRequestContext + default in createRequestContext()
shims/request-store.ts	New — getRequestStore() public API
server/api-handler.ts	Wrap Pages Router API handler in runWithRequestContext (dev server)
entries/pages-server-entry.ts	Wrap Pages Router API handler in _runWithUnifiedCtx (prod/Workers)
package.json	Add "./request-store" export

Motivation

We're running a production SaaS on vinext + Cloudflare Workers (Free plan) with Prisma v7 + Hyperdrive + R2 + NextAuth. We hit the exact alternating-failure pattern from #537 and initially worked around it with a 50ms TTL heuristic. This PR provides the proper framework-level solution.

vinext already has the UnifiedRequestContext + AsyncLocalStorage infrastructure. This PR exposes it to users via a clean public API — 73 lines across 5 files, zero breaking changes.

Test plan

• Verified in production with Prisma v7 + Hyperdrive (zero alternating failures across 500+ requests)
• Outside-scope fallback returns fresh Map each call (prevents cross-call data leakage)
• Happy to add unit tests — let me know the preferred test location

Closes #537

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 625d36e5e7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep middleware request store stable within a request

getRequestStore() returns a brand-new Map whenever isInsideUnifiedScope() is false, which means callers outside a unified scope never see stable per-request state. In Pages Router middleware, execution is wrapped with runWithExecutionContext but not runWithRequestContext, so this branch is always taken there; two getRequestStore() calls in the same middleware invocation won't share data, and values set in middleware cannot be read later in that request path, which breaks the advertised per-request middleware behavior.

Useful? React with 👍 / 👎.

[JamesbbBriz]

/bigbonk review this PR