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

:

           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

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

which is then further incompatible with this local testing?

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

M

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

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

M

MylesBoltonOP•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

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

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

M

MylesBoltonOP•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

J

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

(also known as route handlers in the app dir)

JJames (also known as route handlers in the app dir)

M

MylesBoltonOP•4/6/24, 10:20 PM

yhnx

M

MylesBoltonOP•4/6/24, 10:25 PM

going to make a thread

Lluna did the wrangler push changes get rolled back? i swear i was able to push a next...

L

luna•4/6/24, 10:52 PM

anyone know what’s up with this?

J

James•4/6/24, 11:34 PM

what wrangler changes are you referring to?

JJames what wrangler changes are you referring to?

L

luna•4/7/24, 3:55 AM

https://blog.cloudflare.com/pages-workers-integrations-monorepos-nextjs-wrangler the configure pages with wrangler part.

The Cloudflare Blog

Announcing Pages support for monorepos, wrangler.toml, database int...

Today, we’re launching four improvements to Pages that bring functionality previously restricted to Workers, with the goal of unifying the development experience between the two. Support for monorepos, wrangler.toml, new additions to Next.js support and database integrations!

W

Walshy•4/7/24, 12:41 PM

30 seconds of CPU time

W

Walshy•4/7/24, 12:41 PM

And you can set a lower limit if you wish on the dashboard

W

Walshy•4/7/24, 12:42 PM

10ms is I think still the limit for free plan

W

Walshy•4/7/24, 12:42 PM

Otherwise you're on Standard with 30 seconds

I

Isaac McFadyen•4/7/24, 12:42 PM

Keep in mind this is CPU time

W

Walshy•4/7/24, 12:43 PM

Isaac any idea if free is still 10ms?

I

Isaac McFadyen•4/7/24, 12:43 PM

?cpu-time

F

Flare•4/7/24, 12:43 PM

CPU Time: the amount of work the CPU needs to do, measured in

ms

ms

ms

ms. More CPU-heavy things will increase it (for example, hashing passwords). This is not the same as the time a

fetch

fetch

request takes.
Wall Time: the actual amount of time a Worker runs for, as though you measured it with a clock or your browser DevTools

WWalshy Isaac any idea if free is still 10ms?

I

Isaac McFadyen•4/7/24, 12:43 PM

I believe it is, yeah.

AAnay-208 Ya so cpu time would be cpu * duration, right? how much is the cpu then

I

Isaac McFadyen•4/7/24, 12:44 PM

CPU time is the amount of work the CPU does, it's not the same as duration.

W

Walshy•4/7/24, 12:44 PM

^

I

Isaac McFadyen•4/7/24, 12:44 PM

You can have a Worker running for 30s but only use 10ms CPU time, or have a Worker running for 100ms but use 2s of CPU time.

I

Isaac McFadyen•4/7/24, 12:45 PM

It just depends on what you're doing in the Worker (or Function) itself.

W

Walshy•4/7/24, 12:45 PM

Duration is not related. It's simply an amount of time of actual compute

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

Similar Threads

Similar Threads

Similar Threads