ah, appreciated, thanks 🙏

Is it exacted behaviour for a deployment's functions tab to look like this with sveltekit and a _worker.js output? I can run wrangler pages deployment tail and it connects, but I get no workers logging output?

What's your wrangler version?

2.6.1

Ok that's definitely new enough that there shouldn't be any issues that I know of 🤔

Does the pages functions support service bindings locally? As in the docs claims that they do https://developers.cloudflare.com/pages/platform/functions/bindings/#interact-with-your-service-binding-locally but when I do

npx wrangler pages dev ./public --local --service STUFF=stuff

I get

Unknown argument: service

❯ npx wrangler version
 ⛅️ wrangler 2.6.2

looks like it's wip https://github.com/cloudflare/wrangler2/pull/2162

dang, I got too excited 😆

I made a

.dev.vars

file, which I haven't tested yet, but someone mentioned if I put .env vars there, it'll pick it up for the development.

Probably dumb question, but how do I upgrade my wrangler? Got 2.1.13 and would like to get up to 2.6.2. I tried with

npm update (yada yada)

, even globally on a root folder (no package.json) and it doesn't upgrade versions.

I'm having an issue which I suspect is because of this...

I have the file...

should cover it

It's running 👍

but I get 404...

Already tried all of those.

/cc @kian 👇

you shouldn't be using it globally, it takes your local version

Still happening even after I updated to

2.6.2

...

can you share the content of your functions/api/contact-form file?

Skye helped me in the DMs (so I could share my file). Wanted to leave a note here. Thanks! 🙏

Correct. With a

_worker.js

for toolsets like Remix, Astro, etc, you won't see the functions in the Function tab in the dashboard. Logs should work fine though from the CLI (you won't get them in the dashboard) Do this in your terminal to see logs for the last preview deployment:

wrangler pages deployment tail --environment=preview

Is there any plan to fix this? Been that way for a long time and it seems like a bug

I am building a pages app using astro and cf functions (mostly for fetching data). I noticed that functions work properly when used on the client (i.e. inside

script

tags or components that render on the client) but result in error (500

failed to parse url

) when used on the server (i.e. inside

---

and that gets executed during build stage). Is it normal behaviour? does that mean functions are available only after the build stage?

Yes that's normal. Functions are only available when deployed.

and if I want to fetch data during build I would need to set up a full scale worker?

You can probably just remove the function all together and just fetch whatever data you need in the astro component. 🤷

thank you. understood

i may be missing something obvious but how do i see a breakdown of what projects are using what amount of functions

i didnt expect for any of my sites to be using functions (they all should be static, unless sveltekit decided to change its adapter or something)