are mtls certificate bindings supposed to work?
are mtls certificate bindings supposed to work?
Ni can add it and generate the types fine
Nbut its not on env in runtime
Nneither on
next dev or the previewNwill check in prod, not sure if this is a pages or next-on-pages issue if any
Balso wait.. am i supposed to run next-on-pages with wrangler pages dev? next dev seemed to be working fine all this time
Nwrangler pages dev is for previewing what youve done after you finish with next dev
Bbro you have apple pay on web?
Nyeah
Nahh
Nso i need to go through a worker?
Nyep looks broken in prod too
Ni guess now ill need to figure out how service bindings work :P
D@bun as @neoney just said, you can use
as you can see here: https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/#recommended-development-workflow
next dev for local development, but then preview your app using wrangler pages devnext dev doesn't represent faithully what will run in production)as you can see here: https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/#recommended-development-workflow
Cloudflare Docs
Deploy a full-stack Next.js site (recommended).
Dah, that's super easy 
you just need to add a service binding to your toml file and then you can
you just need to add a service binding to your toml file and then you can
fetchgetRequestContext)Nyep, figuring it all out, all this cloudflare infrastructure is super cool tbh
Nmight not work in next dev ig
Dservice bindings do work there!
Nooh cool, i'm guessing i need to run the second worker in dev still though, right?
Dyes, with
wrangler dev Nwait, how do I get the env into the RPC binding?
N
Nah, ok, this.env
Ncool cool
Ni pray this works
NI see, wrangler types --env-interface doesn't work with this. I need to manually type the functions in?
NI keep getting this error with next dev:
WARNING: Tried to access method or property 'appleFetch' on a Service Binding or Durable Object stub. Are you trying to use RPC? If so, please enable the 'rpc' compat flag or update your compat date to 2024-04-03 or later (see https://developers.cloudflare.com/workers/configuration/compatibility-dates/ ). If you are not trying to use RPC, please note that in the future, this property (and all other property names) will appear to be present as an RPC method.NBut my compat date is
"2024-04-05"?Dah.... yes
RPC/entrypoints are very new so we probably need to update
RPC/entrypoints are very new so we probably need to update
wrangler types, I'll look into that, thanks for pointing it out Dsorry.... I am not sure about this... 
I'd suggest you to open an issue in workers-sdk as this sounds like a bug
(and in the meantime as a workaround use the compat flag?)
I'd suggest you to open an issue in workers-sdk as this sounds like a bug
(and in the meantime as a workaround use the compat flag?)
NI tried the compat flag too ;/
DPS: I haven't yet tried RPC/entrypoints with next-on-pages, please let me know if it works 
Jhttps://docs.google.com/spreadsheets/d/1T7j7FZZO7zmkrEegzhMeMtlFPIh-efYGMc7BuenMPWY/edit?usp=sharing is a great reference fyi for which bindings are supported where 
Nthanks
Nlooks like mtls is wip for pages too
Nwait...
Nthat looks incorrect
Nsays pages functions support mTLS?
Ncouldnt get it to work
NTo interact with a Service binding while developing locally, run the Worker you want to bind to via wrangler dev and in parallel, run wrangler pages dev with --service <BINDING_NAME>=<SCRIPT_NAME> where SCRIPT_NAME indicates the name of the Worker. For example, if your Worker is called my-worker, connect with this Worker by running it via npx wrangler dev (in the Worker’s directory) alongside npx wrangler pages dev <OUTPUT_DIR> --service MY_SERVICE=my-worker (in the Pages’ directory). Interact with this binding by using context.env (for example, context.env.MY_SERVICE).
Nmaybe it aint that simple
Dlol ok that makes it sound more complicated than it is
Nfr
Nlet me try running it in preview with that flag added
Nwelp. there really isnt additional logging
D@neoney regarding the service binding, maybe this can help (although it is a bit outdated): https://github.com/dario-piotrowicz/next-on-pages-next-dev-get-bindings-proxy-test-demo
GitHub
Contribute to dario-piotrowicz/next-on-pages-next-dev-get-bindings-proxy-test-demo development by creating an account on GitHub.
Ntbf i can just use a fetch binding
Ni only have like 1 request i need to proxy
Nill just not use rpc
Ndoesnt work either.... wtf
