Dyeah that's not going to work 
(I did try to convince the team to fix this but it seems like people are happy with the current way of not reading the
)
(I did try to convince the team to fix this but it seems like people are happy with the current way of not reading the
.envyes, you should have a
.dev.vars.envCloudflare Docs
Store sensitive information, like API keys and auth tokens, in your Worker.
Bthats fine im ok with that, but its crucial that these edge cases should be documented in a single place somwhere as a lot of nextjs devs will run into these kind of issues
Dyes.... that's a totally valid point....
Band i dont think a lot of people will play close attention to github docs as not a lot of people use github for docs, maybe have a separate website for this? idk
DGitHub
It would be very convenient if https://developers.cloudflare.com/pages/framework-guides/deploy-a-nextjs-site/ also mentioned that for Next.js (and its command dev) you can use the .env file as usua...
Dyes I can see your point.... we did add a troubleshooting section to our Next.js guide: https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/#troubleshooting
Cloudflare Docs
Deploy a full-stack Next.js site (recommended).
DI guess I should add this there too 
Bis
cache supported btw?B
Bthis^
DI would definitely say yes, but I can't guarantee it, I'd give it a try and see if it works 
Nare 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 devwill 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 devwrangler pages dev to make sure everything works as you'd expect it to (since next devas 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 devwait, 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...
