and i dont think a lot of people will play close attention to github docs as not a lot of people use

D

Dario•4/8/24, 9:34 PM

https://github.com/cloudflare/next-on-pages/issues/604

GitHub

Documentation: Environment variables · Issue #604 · cloudflare/next...

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...

Bbun and i dont think a lot of people will play close attention to github docs as not...

D

Dario•4/8/24, 9:35 PM

yes 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

Full-stack deployment · Cloudflare Pages docs

Deploy a full-stack Next.js site (recommended).

D

Dario•4/8/24, 9:36 PM

I guess I should add this there too

B

bunOP•4/8/24, 9:36 PM

is

cache

cache

supported btw?

B

bunOP•4/8/24, 9:36 PM

B

bunOP•4/8/24, 9:36 PM

this^

D

Dario•4/8/24, 9:38 PM

I would definitely say yes, but I can't guarantee it, I'd give it a try and see if it works

N

neoney•4/8/24, 9:47 PM

are mtls certificate bindings supposed to work?

N

neoney•4/8/24, 9:47 PM

i can add it and generate the types fine

N

neoney•4/8/24, 9:47 PM

but its not on env in runtime

N

neoney•4/8/24, 9:47 PM

neither on

next dev

next dev

next dev

next dev or the preview

N

neoney•4/8/24, 9:48 PM

will check in prod, not sure if this is a pages or next-on-pages issue if any

B

bunOP•4/8/24, 9:48 PM

also wait.. am i supposed to run next-on-pages with wrangler pages dev? next dev seemed to be working fine all this time

N

neoney•4/8/24, 9:49 PM

wrangler pages dev is for previewing what youve done after you finish with next dev

B

bunOP•4/8/24, 9:49 PM

bro you have apple pay on web?

N

neoney•4/8/24, 9:49 PM

yeah

Nneoney are mtls certificate bindings supposed to work?

D

Dario•4/8/24, 9:50 PM

@neoney mtls certificates are not supported (since they are not in pages)

N

neoney•4/8/24, 9:50 PM

ahh

N

neoney•4/8/24, 9:51 PM

so i need to go through a worker?

N

neoney•4/8/24, 9:51 PM

yep looks broken in prod too

N

neoney•4/8/24, 9:53 PM

i guess now ill need to figure out how service bindings work :P

D

Dario•4/8/24, 9:53 PM

@bun as @neoney just said, you can use

next dev

next dev

next dev

next dev for local development, but then preview your app using

wrangler pages dev

wrangler pages dev

to make sure everything works as you'd expect it to (since

next dev

next dev

next dev

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

Full-stack deployment · Cloudflare Pages docs

Deploy a full-stack Next.js site (recommended).

Nneoney i guess now ill need to figure out how service bindings work :P

D

Dario•4/8/24, 9:54 PM

ah, that's super easy

you just need to add a service binding to your toml file and then you can

fetch

fetch

from that binding (which you get from

getRequestContext

getRequestContext

getRequestContext

getRequestContext)

N

neoney•4/8/24, 9:54 PM

yep, figuring it all out, all this cloudflare infrastructure is super cool tbh

N

neoney•4/8/24, 9:55 PM

might not work in next dev ig

Nneoney might not work in next dev ig

D

Dario•4/8/24, 9:55 PM

service bindings do work there!

N

neoney•4/8/24, 9:55 PM

ooh cool, i'm guessing i need to run the second worker in dev still though, right?

D

Dario•4/8/24, 9:56 PM

yes, with

wrangler dev

wrangler dev

N

neoney•4/8/24, 9:57 PM

wait, how do I get the env into the RPC binding?

N

neoney•4/8/24, 9:57 PM

N

neoney•4/8/24, 9:57 PM

ah, ok, this.env

N

neoney•4/8/24, 9:57 PM

cool cool

N

neoney•4/8/24, 9:58 PM

i pray this works

N

neoney•4/8/24, 9:59 PM

I see, wrangler types --env-interface doesn't work with this. I need to manually type the functions in?

N

neoney•4/8/24, 10:03 PM

I 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.

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.

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.

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.

N

neoney•4/8/24, 10:03 PM

But my compat date is

"2024-04-05"

"2024-04-05"

"2024-04-05"

"2024-04-05"?

Nneoney I see, wrangler types --env-interface doesn't work with this. I need to manually...

D

Dario•4/8/24, 10:03 PM

ah.... yes

RPC/entrypoints are very new so we probably need to update

wrangler types

wrangler types

wrangler types

wrangler types, I'll look into that, thanks for pointing it out

Nneoney I keep getting this error with next dev: `WARNING: Tried to access method or pro...

D

Dario•4/8/24, 10:05 PM

sorry.... 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?)

N

neoney•4/8/24, 10:05 PM

I tried the compat flag too ;/

D

Dario•4/8/24, 10:05 PM

PS: I haven't yet tried RPC/entrypoints with next-on-pages, please let me know if it works

Nneoney so i need to go through a worker?

J

James•4/8/24, 10:06 PM

https://docs.google.com/spreadsheets/d/1T7j7FZZO7zmkrEegzhMeMtlFPIh-efYGMc7BuenMPWY/edit?usp=sharing is a great reference fyi for which bindings are supported where

N

neoney•4/8/24, 10:06 PM

thanks

N

neoney•4/8/24, 10:07 PM

looks like mtls is wip for pages too

N

neoney•4/8/24, 10:07 PM

wait...

N

neoney•4/8/24, 10:07 PM

that looks incorrect

N

neoney•4/8/24, 10:07 PM

says pages functions support mTLS?

N

neoney•4/8/24, 10:07 PM

couldnt get it to work

N

neoney•4/8/24, 10:09 PM

To 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).

N

neoney•4/8/24, 10:09 PM

maybe it aint that simple

D

Dario•4/8/24, 10:10 PM

lol ok that makes it sound more complicated than it is

and i dont think a lot of people will play close attention to github docs as not a lot of people use

Similar Threads