process.env.DBgetRequestContext().env.DB
D
, I'll look into that as soon as I can
BBD
env.d.ts doesn't matter too much, in your code you can do: (process.env as any).DB and see if it contains the binding BBBDgetOptionalRequestContext instead of process.env?
G
BBB
E
CB
DgetRequestContext be used for production bindings (deployed on Cloudflare pages) or only local development?BDBBD
getRequestContextBD
)D
B
getRequestContext is only for dev ?
Z_middleware.ts file inside a functions folder. I created it and for now I just tried to return the sample response and also some console.logs to see if this was working but I can't see anything working.
J@cloudflare/next-on-pages, the functions directory won't work as we build our own worker for your project. You could try using Next.js API route handlers or Next.js middleware instead
W
L
BD
setupDevPlatform: https://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev#next-on-pages-next-dev setupDevBindings it is exactly the same besides the function's name and the fact that you define your bindings in a wrangler.toml
)DsetupDevPlatform documentation?D
: https://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev#next-on-pages-next-dev
getPlatformProxy (and we do defer to that page in our docs)WDD
WWWD DWDWDWDW
Menv.d.ts(process.env as any).DBgetOptionalRequestContextprocess.envgetRequestContextgetRequestContextgetRequestContext_middleware.ts functions@cloudflare/next-on-pagessetupDevPlatformsetupDevPlatformsetupDevBindingsgetPlatformProxy[[durable_objects.bindings]]
name = "MY_DO"
script_name = "do-worker"
class_name = "DurableObjectClass"import { drizzle } from "drizzle-orm/d1";
export const runtime = "edge";
const db = drizzle((process.env as any).DB);
export { db };