- Cloudflare Developers

P

Pat BranchaudOP•4/5/24, 8:39 PM

FYI : It's a long journey for Felix, and Philippe and I we all work on the same project

PPat Branchaud Click to see attachment

N

Nob•4/5/24, 8:40 PM

I think "force-cache" is self explaining of its function

N

Nob•4/5/24, 8:40 PM

i dont understand your question

P

Pat BranchaudOP•4/5/24, 8:41 PM

not a question, I meant thank you it seems to work

PPat Branchaud not a question, I meant thank you it seems to work

N

Nob•4/5/24, 8:42 PM

ahhh okay long journey for me too lul

P

Pat BranchaudOP•4/5/24, 8:42 PM

2 days of searching and then the trex head solves it with 2 words

N

Nob•4/5/24, 8:43 PM

also you should add a KV binding named

__NEXT_ON_PAGES__KV_SUSPENSE_CACHE

__NEXT_ON_PAGES__KV_SUSPENSE_CACHE

__NEXT_ON_PAGES__KV_SUSPENSE_CACHE

__NEXT_ON_PAGES__KV_SUSPENSE_CACHE

N

Nob•4/5/24, 8:43 PM

because without it, caching is only at datacenter level

NNob also you should add a KV binding named ``__NEXT_ON_PAGES__KV_SUSPENSE_CACHE``

S

SeeringPhil•4/5/24, 8:44 PM

Yeah, the binding was already in place but no keys were saved before the force-cache

N

Nob•4/5/24, 8:45 PM

@Pat Branchaud no i'm not consulting or freelance x)

N

Nob•4/5/24, 8:45 PM

i'm doing gaming websites

F

FelDev•4/5/24, 8:45 PM

Thanks a lot though, seriously.

J

James•4/5/24, 9:00 PM

IIRC force-cache is supposed to be the default but I guess we probably need to do some logic to apply it if no cache value is specified.

I'd be a bit hesitant to add that in now though considering we've had our fetch cache live for like 8 months and that kind of change would probably be breaking for a lot of users

J

James•4/5/24, 9:02 PM

it's one of those things that would technically be a bug fix but in actuality would be a breaking change for almost all users who use fetch on the server

P

Pat BranchaudOP•4/5/24, 9:03 PM

could be added to documentation

NNob <@836762764672106586> no i'm not consulting or freelance x)

P

Pat BranchaudOP•4/5/24, 9:12 PM

Hey Nob, if you ever find yourself in Sherbrooke, QC, Canada, hit me up, free beer on me!

PPat Branchaud Hey Nob, if you ever find yourself in Sherbrooke, QC, Canada, hit me up, free be...

N

Nob•4/5/24, 9:23 PM

ahah, France is a bit far from Canada but maybe in 10 years x)

N

Nob•4/5/24, 9:23 PM

I forgot I'm not even old enough to drink

N

Nob•4/5/24, 9:23 PM

P

Pat BranchaudOP•4/5/24, 9:38 PM

là je comprends pourquoi tu ne comprenais pas quand je parle comme Yoda dogekek

M

MylesBolton•4/6/24, 12:42 AM

hey where do i put my functions for the cloudflare pages plugins

M

MylesBolton•4/6/24, 12:42 AM

is it in the root dir or should i put inside /src or /src/app

MMylesBolton hey where do i put my functions for the cloudflare pages plugins

N

Nob•4/6/24, 1:13 AM

/app/api and you create api routes

NNob /app/api and you create api routes

M

MylesBolton•4/6/24, 2:24 AM

cool

T

thanhle•4/6/24, 6:04 AM

do we have timeout for worker or page functions or nextjs api route?

M

MylesBolton•4/6/24, 6:38 AM

do tell me if im being dumb but anyone got any ideas what i did wrong ?

T

thipperz•4/6/24, 8:42 AM

This error keeps happening even after I add

compatibility_date = "2024-04-06"

compatibility_date = "2024-04-06"

compatibility_date = "2024-04-06"

compatibility_date = "2024-04-06" to my wrangler.toml.

What could I be missing? I tried updating wrangler and workers types

Tthipperz This error keeps happening even after I add `compatibility_date = "2024-04-06"` ...

H

Hello, I’m Allie!•4/6/24, 8:44 AM

That looks like something else? I’m guessing that whatever you are calling ImageService on isn’t actually supposed to be a binding?

MMylesBolton do tell me if im being dumb but anyone got any ideas what i did wrong ?

J

James•4/6/24, 10:42 AM

You could probably just try implementing the server side validation example in the turnstile docs - https://developers.cloudflare.com/turnstile/get-started/server-side-validation/

Pages plugins will likely not work properly in Next.js api routes because they are written under the assumption that they'll be running in the functions directory, whereas here you just need a standard js solution instead

L

luna•4/6/24, 11:53 AM

did the wrangler push changes get rolled back? i swear i was able to push a next on pages project without needing to setup anything in the dashboard in the last few days but now im back to needing todo that.

L

luna•4/6/24, 11:59 AM

also seems like metrics arent being recorded at all for this deploy.

are metrics delayed?

Screenshot_2024-04-06_at_10.28.35_pm.png

J

James•4/6/24, 2:42 PM

probably better for pages-help

Lluna also seems like metrics arent being recorded at all for this deploy. 🤔 are me...

U

Unsmart•4/6/24, 5:08 PM

Trying looking at the 30min chart sometimes that one is faster to populate

U

Unsmart•4/6/24, 5:08 PM

Or whatever the shortest range of time is

J

James•4/6/24, 5:45 PM

Any version of Next.js 14 should be perfectly fine

T

thipperz•4/6/24, 6:43 PM

i'm trying to access a Service binding (RPC) in my Next-on-Pages. My wrangler.toml looks like this:

# Generated by Wrangler
name = "tx"
pages_build_output_dir = ".vercel/output/static"
compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat"]

[[services]]
binding = "VECTORIZE_WORKER"
service = "vectorize-worker"
environment = "production"

[env.production]
compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat" ]

  [[env.production.services]]
  binding = "VECTORIZE_WORKER"
  service = "vectorize-worker"
  environment = "production"

# Generated by Wrangler
name = "tx"
pages_build_output_dir = ".vercel/output/static"
compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat"]

[[services]]
binding = "VECTORIZE_WORKER"
service = "vectorize-worker"
environment = "production"

[env.production]
compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat" ]

  [[env.production.services]]
  binding = "VECTORIZE_WORKER"
  service = "vectorize-worker"
  environment = "production"

# Generated by Wrangler
name = "tx"
pages_build_output_dir = ".vercel/output/static"
compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat"]

[[services]]
binding = "VECTORIZE_WORKER"
service = "vectorize-worker"
environment = "production"

[env.production]
compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat" ]

  [[env.production.services]]
  binding = "VECTORIZE_WORKER"
  service = "vectorize-worker"
  environment = "production"

# Generated by Wrangler
name = "tx"
pages_build_output_dir = ".vercel/output/static"
compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat"]

[[services]]
binding = "VECTORIZE_WORKER"
service = "vectorize-worker"
environment = "production"

[env.production]
compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat" ]

  [[env.production.services]]
  binding = "VECTORIZE_WORKER"
  service = "vectorize-worker"
  environment = "production"

When I call it like this, running

next dev

next dev

next dev

next dev:

           const { env } = getRequestContext()
            const VECTORIZE_WORKER = env.VECTORIZE_WORKER
            if (!VECTORIZE_WORKER)
                throw new Error('UNDEFINED BINDING: VECTORIZE_WORKER')
            const response = await VECTORIZE_WORKER.ImageSearch(imagename)

           const { env } = getRequestContext()
            const VECTORIZE_WORKER = env.VECTORIZE_WORKER
            if (!VECTORIZE_WORKER)
                throw new Error('UNDEFINED BINDING: VECTORIZE_WORKER')
            const response = await VECTORIZE_WORKER.ImageSearch(imagename)

           const { env } = getRequestContext()
            const VECTORIZE_WORKER = env.VECTORIZE_WORKER
            if (!VECTORIZE_WORKER)
                throw new Error('UNDEFINED BINDING: VECTORIZE_WORKER')
            const response = await VECTORIZE_WORKER.ImageSearch(imagename)

           const { env } = getRequestContext()
            const VECTORIZE_WORKER = env.VECTORIZE_WORKER
            if (!VECTORIZE_WORKER)
                throw new Error('UNDEFINED BINDING: VECTORIZE_WORKER')
            const response = await VECTORIZE_WORKER.ImageSearch(imagename)

It does not throw this error, indicating that the binding was found, but I get the following warning regarding RPC:

WARNING: Tried to access method or property 'ImageSearch' 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

WARNING: Tried to access method or property 'ImageSearch' 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

WARNING: Tried to access method or property 'ImageSearch' 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

WARNING: Tried to access method or property 'ImageSearch' 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

The "Image Search" is defined in my worker like this:

export default class extends WorkerEntrypoint {
    async ImageSearch(imagename: string) {
        return new Response('Got results', { status: 200 })
    }
}

export default class extends WorkerEntrypoint {
    async ImageSearch(imagename: string) {
        return new Response('Got results', { status: 200 })
    }
}

export default class extends WorkerEntrypoint {
    async ImageSearch(imagename: string) {
        return new Response('Got results', { status: 200 })
    }
}

export default class extends WorkerEntrypoint {
    async ImageSearch(imagename: string) {
        return new Response('Got results', { status: 200 })
    }
}

It does work when running

wrangler pages dev .vercel/output/static --service VECTORIZE_WORKER=vectorize-worker --compatibility-flag=nodejs_compat"

wrangler pages dev .vercel/output/static --service VECTORIZE_WORKER=vectorize-worker --compatibility-flag=nodejs_compat"

wrangler pages dev .vercel/output/static --service VECTORIZE_WORKER=vectorize-worker --compatibility-flag=nodejs_compat"

wrangler pages dev .vercel/output/static --service VECTORIZE_WORKER=vectorize-worker --compatibility-flag=nodejs_compat" alongside the service worker running via

wrangler dev

wrangler dev

It does not work (and throws the error above) when running

next dev

next dev

next dev

next dev

Is it possible to make rpc service bindings work via next dev? Also since my vectorize worker do access Vectorize, it will only work via

wrangler dev --remote

wrangler dev --remote

wrangler dev --remote

wrangler dev --remote which is then further incompatible with this local testing?

JJames You could probably just try implementing the server side validation example in t...

M

MylesBolton•4/6/24, 7:00 PM

Ah OK do you think the mail channels plugin will work as well ?

M

MylesBolton•4/6/24, 7:00 PM

Or do you think I should just selfhost the website with nodemailer

D

DreamingGod•4/6/24, 8:10 PM

hey i got quick question

D

DreamingGod•4/6/24, 8:10 PM

is the 1 MiB limit per function or for the whole site?

D

DreamingGod•4/6/24, 8:14 PM

how do you debug/break down ur bundle size?

DDreamingGod is the 1 MiB limit per function or for the whole site?

H

Hello, I’m Allie!•4/6/24, 8:16 PM

For the whole server bundle. This doesn't include static assets though. And the limit can be increased with a Workers Paid plan

D

DreamingGod•4/6/24, 8:16 PM

ye im thinking about buying the 10 MiB limit but even that seems very low as i have a simple app but already at 5 MiB

J

James•4/6/24, 8:28 PM

If you have a rather simple app at 5mb, maybe you have some chonky dependencies that are polluting the bundle

UUnsmart Trying looking at the 30min chart sometimes that one is faster to populate

L

luna•4/6/24, 8:51 PM

even if change it to 15 mins it’s not live as i was expecting.

JJames You could probably just try implementing the server side validation example in t...

M

MylesBolton•4/6/24, 10:18 PM

where would i put the functions dir in a nextjs application using the app directory?

M

MylesBolton•4/6/24, 10:19 PM

somone said just put them in /src/app/api

MMylesBolton where would i put the functions dir in a nextjs application using the app direct...

J

James•4/6/24, 10:19 PM

You would use Next.js API routes. The functions directory is not compatible with next-on-pages

Similar Threads