thanks, I'll give it a try 🙂 (but yeah a repro would definitely speed things up 🙏)
thanks, I'll give it a try 
(but yeah a repro would definitely speed things up 
)
(but yeah a repro would definitely speed things up )
BGitHub
Contribute to sunneydev/next-on-pages-env-bug-repro development by creating an account on GitHub.
Bhere
Bseems like its only for environment variables
Bthat are defined in
.envBor maybe for other ones as well, not sure exactly
Bah the action doesn't work as well, no need 3rd (utility) layer at all
Bso like its for
.env files that are locally defined i guess,Bnextjs accounts for them in process.env but not
getRequestContext() i guess
Doh....
Btldr bindings work, env variables defined in
.env dont. with getRequestContext() locallyDyou're not using
.dev.vars are you...?Bnope, regular
.envB.dev.vars woudl work?
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
.env file )Dyes, you should have a
.dev.vars file that contains the exact same content as your .env fileDCloudflare 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 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 dev to make sure everything works as you'd expect it to (since next 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
fetch from that binding (which you get from getRequestContext)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