B
D
node:async_hookswrangler deploy
if so please let me know as that needs amending! 
BB
DWorkersPagesPages
BBDwrangler pages deploy@cloudflare/next-on-pages.vercel/output/static/_worker.js
BBD
BDHow do you get the env in a non request?all your source code is run inside a Cloudflare worker request handler, so you're basically always handling a request (i.e. you should always be able to run
getRequestContext
drizzlegetOptionalRequestContextI managed to get next-on-pages -> drizzle -> d1 working with next auth for creating my users, so it was working fine for me? Weirdok, maybe sometimes/in some cases it works.... I really don't know to be honest
(but if it works for you great! 
)DBut when I was using process.env it worked on production but not locally and now that I am using env and getRequestContext it works locally but not in production lol
.envnext devwrangler pages devMy .env file atm has nothing in it related to bindingsweird
env.d.ts.envprocess.env.DBgetRequestContext().env.DB
, I'll look into that as soon as I canBBDenv.d.ts(process.env as any).DBgetOptionalRequestContextprocess.env
GBBB
E
CB
DgetRequestContext
import { getRequestContext } from "@cloudflare/next-on-pages";
import { drizzle } from "drizzle-orm/d1";
export const runtime = 'edge';
const { env } = getRequestContext();
const db = drizzle(env.DB);
export { db };env.d.ts
declare global {
namespace NodeJS {
interface ProcessEnv {
DB: D1Database;
DOCUMENTS_BUCKET: R2Bucket;
}
}
}
export {}env.d.ts
interface CloudflareEnv {
DB: D1Database;
DOCUMENTS_BUCKET: R2Bucket;
}import { drizzle } from "drizzle-orm/d1";
export const runtime = "edge";
const db = drizzle((process.env as any).DB);
export { db };