I keep getting this error with next dev: `WARNING: Tried to access method or property 'appleFetch' o

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.

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

But my compat date is "2024-04-05""2024-04-05"?

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

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

ah.... yes

RPC/entrypoints are very new so we probably need to update wrangler typeswrangler 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...

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

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

I tried the compat flag too ;/

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?

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

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

thanks

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

looks like mtls is wip for pages too

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

wait...

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

that looks incorrect

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

says pages functions support mTLS?

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

couldnt get it to work

neoneyOP•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).

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

maybe it aint that simple

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

lol ok that makes it sound more complicated than it is

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

neoneyOP•4/8/24, 10:11 PM

let me try running it in preview with that flag added

neoneyOP•4/8/24, 10:11 PM

welp. there really isnt additional logging

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

@neoney regarding the service binding, maybe this can help (although it is a bit outdated): https://github.com/dario-piotrowicz/next-on-pages-next-dev-get-bindings-proxy-test-demo

GitHub

GitHub - dario-piotrowicz/next-on-pages-next-dev-get-bindings-proxy...

Contribute to dario-piotrowicz/next-on-pages-next-dev-get-bindings-proxy-test-demo development by creating an account on GitHub.

neoneyOP•4/8/24, 10:12 PM

tbf i can just use a fetch binding

neoneyOP•4/8/24, 10:12 PM

i only have like 1 request i need to proxy

neoneyOP•4/8/24, 10:12 PM

ill just not use rpc

neoneyOP•4/8/24, 10:15 PM

doesnt work either.... wtf

neoneyOP•4/8/24, 10:15 PM

⨯ TypeError: Cannot read properties of undefined (reading 'fetch')
at Object.fetch (/home/neoney/code/sellhub/sellhub-checkout/apps/worker/src/index.ts:29:37)
at fetchDispatcher (/home/neoney/code/sellhub/sellhub-checkout/apps/worker/.wrangler/tmp/bundle-oEZVUv/middleware-loader.entry.ts:56:17)

neoneyOP•4/8/24, 10:16 PM

also, for some reason when logging the binding it says constructor { }constructor { }

Nneoney ⨯ TypeError: Cannot read properties of undefined (reading 'fetch') at Object...

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

are you running the worker with

wrangler dev

wrangler dev

neoneyOP•4/8/24, 10:17 PM

yep

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

is the name of the worker correct? have you restarted

next dev

next dev

neoneyOP•4/8/24, 10:17 PM

services.service matches the workers name field

neoneyOP•4/8/24, 10:18 PM

and wrangler pages dev crashes....

neoneyOP•4/8/24, 10:18 PM

neoneyOP•4/8/24, 10:18 PM

maybe ill try updating deps

Nneoney Click to see attachment

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

can you also share the worker's toml?

neoneyOP•4/8/24, 10:19 PM

name = "workername"
main = "src/index.ts"
compatibility_date = "2024-04-05"
compatibility_flags = ["nodejs_compat"]

[triggers]
crons = ["* * * * *"]

[[mtls_certificates]]
binding = "APPLE_PAY_CERT"
certificate_id = "censored"

name = "workername"
main = "src/index.ts"
compatibility_date = "2024-04-05"
compatibility_flags = ["nodejs_compat"]

[triggers]
crons = ["* * * * *"]

[[mtls_certificates]]
binding = "APPLE_PAY_CERT"
certificate_id = "censored"

neoneyOP•4/8/24, 10:21 PM

this so confusing

neoneyOP•4/8/24, 10:21 PM

console.log(env.WORKER) - constructor {}
console.log(new env.WORKER()) - env.WORKER is not a constructor

neoneyOP•4/8/24, 10:21 PM

Nneoney ```toml name = "workername" main = "src/index.ts" compatibility_date = "2024-04-...

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

the name of the worker doesn't match the name you used in the command you shared above

neoneyOP•4/8/24, 10:22 PM

it does match, i edited it

neoneyOP•4/8/24, 10:22 PM

name = "sellhub-checkout-cron"
in the toml actually

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

lol ok, I should have figured

neoneyOP•4/8/24, 10:23 PM

typeof env.WORKER is object

neoneyOP•4/8/24, 10:23 PM

and env.WORKER.fetch says cannot read properties of undefined (reading 'fetch')

neoneyOP•4/8/24, 10:23 PM

most consistent programming language

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

that doesn't make much sense

(typeof undefined !== object)

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

yeah i have no clue

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

can you have a typo somewhere in there?

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

autogenerated types

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

so i doubt

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

[[services]]
binding = "WORKER"
service = "sellhub-checkout-cron"

[[services]]
binding = "WORKER"
service = "sellhub-checkout-cron"

in the pages wrangler.toml

I keep getting this error with next dev: `WARNING: Tried to access method or property 'appleFetch' o

Similar Threads

Similar Threads

Similar Threads