[BUG] worker binding cannot be exposed

[AugustinMauroy]

Describe the bug

context

If you want to e2e test you authed next app that use better auth you may use https://better-auth.com/docs/plugins/test-utils with you prisma that use CF binding https://opennext.js.org/cloudflare/howtos/db#prisma-orm

Issue

when calling auth utilizes it's throw ERROR: getCloudflareContexthas been called without having calledinitOpenNextCloudflareForDev from the Next.js config file.

Why ?

Because test with playwright are ruined in node.js context and not in next/open-next/wrangler context. which create an issue because auth utility cannot use prisma client because he didn't have D1

Solution

Having api that feed playwright env. I'm pretty sure that it's already exist but that's a lack of docs.

Steps to reproduce

1. run test
2. see the error

Expected behavior

test utile work correctly with prisma client that use d1 binding to interact with same d1 than dev server

@opennextjs/cloudflare version

1.19.9"

Wrangler version

4.90.0

next info output

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.3.0: Wed Jan 28 20:53:31 PST 2026; root:xnu-12377.91.3~2/RELEASE_ARM64_T8103
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 25.7.0
  npm: 11.10.1
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 16.2.6 // Latest available version is detected (16.2.6).
  eslint-config-next: N/A
  react: 19.2.6
  react-dom: 19.2.6
  typescript: 6.0.3
Next.js Config:
  output: N/A

Additional context

No response

[AugustinMauroy]

the potential solution is:

import { getPlatformProxy } from "wrangler";

const cloudflareContext = await getPlatformProxy();
globalThis[Symbol.for("__cloudflare-context__")] = cloudflareContext;
globalThis.__cloudflareContext__ = cloudflareContext;

export default async function globalSetup() {}

[AugustinMauroy]

I think it's because

opennextjs-cloudflare/packages/cloudflare/src/api/cloudflare-context.ts

Line 275 in f07200e

function shouldContextInitializationRun(): boolean {

function send false on playwright context

[vicb]

Please add a minimal repro (link to a GH repository and steps to reproduce the issue).

[AugustinMauroy]

I'm going to do that

[AugustinMauroy]

I hope it's suffisant https://github.com/AugustinMauroy/opennextjs-cloudflare-issue-1264

[AugustinMauroy]

okay found something. to force opennext to populate global this we need to do NEXT_RUNTIME=\"nodejs\" playwright test but now I have new issues The loaded wasm module was unexpectedly undefinedornull once loaded on prisma side

I'm deep-diving. I think there are maybe no bug but need a guide

[AugustinMauroy]

okay last word is

1. enabling env

because of how opennext work. you need to add NEXT_RUNTIME=nodejs to env variable so in this case openest will populate the globalthis on nodejs env when calling getCloudflareContext

2. using prisma

prisma work differently with different runtime as expected.

1. if you are using cloudflare runtime the test with playwright will fails because it's designed to work on cf and not on node as expected
2. if you are using nodejs it's will use node:url which is breaking the middleware so you next app don't work

tempary solution: using 2 generator one for nodejs (test) and one for next.js /cf (prod)

generator client {
  provider        = "prisma-client"
  output          = "../src/generated"
  runtime         = "cloudflare"
}

generator testClient {
  provider        = "prisma-client"
  output          = "../src/generated-test"
  runtime         = "nodejs"
}

and prisma.ts

import { getCloudflareContext } from "@opennextjs/cloudflare";
import { cache } from "react";
import { PrismaD1 } from "@prisma/adapter-d1";


const prismaClientModule = process.env.NODE_ENV === "test" ? "#/generated-test/client" : "#/generated/client";
const { PrismaClient } = await import(prismaClientModule);

const getPrisma = cache(async () => {
	const { env } = await getCloudflareContext({ async: true });
	const adapter = new PrismaD1(env.DB);

	return new PrismaClient({
		adapter,
		log:
			process.env.NEXTJS_ENV === "development"
				? ["query", "error", "warn"]
				: ["error"],
	});
});

const getPrismaSync = cache(() => {
	const { env } = getCloudflareContext({ async: false });
	const adapter = new PrismaD1(env.DB);

	return new PrismaClient({
		adapter,
		log:
			process.env.NEXTJS_ENV === "development"
				? ["query", "error", "warn"]
				: ["error"],
	});
});

export const prisma = await getPrisma();
export const prismaSync = getPrismaSync();

Act to take

1. wait for proxy.ts => it's will allow to use compatible APIs on worker so nodejs prisma runtime will work and we will have one Prisma Client
2. document the NEXT_RUNTIME=nodejs behavior
3. add docs about edge cases when you will need 2 generator to access to same D1 instance for dev/test env !not prod!