I put it at project root .. now on same directory as functions .. still same. Let me try --persist now see what happens

Thanks for your patience .. that worked

I put it at project root .. now on same directory as functions .. still same. Let me try --persist now see what happens YES !!!!!😆 💯 Thanks for your patience .. that worked I guess the problem is that I could not find the documentation for --persist using

npx wrangler -h

yeah

You can find it here https://developers.cloudflare.com/workers/wrangler/commands/

What I've done is just have a route like

/seed-user

and have the worker put in whatever you need. I've also added an authentication check to this to make sure no one can randomly hit this route.

Hi Folks, a new question. I'm trying to pass on data from my middleware authenticator to my api. I put data in context.data and then call context.next(). In the middleware I verify that there is data in context.data with a console.log. However, when my api function is subsequently called, context.data is empty. Any thoughts on how to make this work? I also noticed that context.next has a couple of parameters, and was wondering if these would have any effect, but I can't find much information on what the effect of these parameters are.

Thanks for the response, Justin.

It seems this may be a bug according to the response here: https://community.cloudflare.com/t/what-is-context-data-in-pages-functions/476559/5

There's an explanation here https://github.com/cloudflare/workers-sdk/issues/2797

TLDR, don't use

context.data = { ... }

, but instead

context.data.foo = ...

Yes .. fantastic .. that solved it.💯

is there any way to debug deployed functions? I'm getting

Internal Error

when its deployed to cloudflare pages, but when I test locally (using wrangler) it works perfectly.

?pages-logs

If you're looking to tail a Pages Function you can do so in the UI here: https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/:pages-deployment/functions or with Wrangler:

wrangler pages deployment tail [deploymentId/url]

this will let you stream the logs, if you reproduce the error while streaming logs you should see the exception in there

ah, thank you. i swear i looked around the ui for like 30 mins but couldnt find that 😄

hm, why would i be getting a code 1003 to a request of a non-cloudflare domain?

Are you trying to

fetch('some.ip.address')

?

Can you share your code? You can't

fetch

direct IP addresses for example though

ah ok good to know

yes i am

Yeah unfortunately that won't work. You'll need to create a DNS record for it

i actually already had one for it, just the ip address was easier access at the time 😅

hm, now i have a slightly different issue. When testing locally using wrangler, it receives json data perfectly, but when deployed, it just receives an empty string (but I see no request on the server its contacting)

does it need to be https or something?

I have this code for debugging:

js
const userDataRaw = await fetch("http://my.domain.com:25394/getInfo?id=" + encodeURIComponent(id))
    .then(r => r.text());
console.log("response: " + userDataRaw);

Custom ports don't really work either

hm, ok then

guess ive got to set up an origin rule or something 😄