Does the pages functions support service bindings locally? As in the docs claims that they do https:

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

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

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

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

Unknown argument: service

Unknown argument: service

Unknown argument: service

Unknown argument: service

❯ npx wrangler version
 ⛅️ wrangler 2.6.2

❯ npx wrangler version
 ⛅️ wrangler 2.6.2

❯ npx wrangler version
 ⛅️ wrangler 2.6.2

❯ npx wrangler version
 ⛅️ wrangler 2.6.2

NipsuliOP•12/12/22, 6:04 PM

dang, I got too excited

NNipsuli Does the pages functions support service bindings locally? As in the docs claims...

Chinoman10•12/12/22, 6:15 PM

I made a

.dev.vars

.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.

Chinoman10•12/12/22, 6:17 PM

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)npm update (yada yada), even globally on a root folder (no package.json) and it doesn't upgrade versions.

Chinoman10•12/12/22, 6:17 PM

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

Chinoman10•12/12/22, 6:17 PM

I have the file...

kian•12/12/22, 6:18 PM

https://developers.cloudflare.com/workers/wrangler/install-and-update/#update-wrangler should cover it

CChinoman10 I have the file...

Chinoman10•12/12/22, 6:18 PM

It's running

Chinoman10•12/12/22, 6:18 PM

but I get 404...

Kkian <https://developers.cloudflare.com/workers/wrangler/install-and-update/#update-w...

Chinoman10•12/12/22, 6:19 PM

Already tried all of those.

CChinoman10 Already tried all of those.

Chinoman10•12/12/22, 6:19 PM

/cc @kian | DevDocs

CChinoman10 but I get 404...

Chinoman10•12/12/22, 6:25 PM

Still happening even after I updated to

2.6.2

2.6.2

...

Chinoman10•12/12/22, 6:40 PM

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

SSparrow Is it exacted behaviour for a deployment's functions tab to look like this with ...

JustinNoel•12/12/22, 8:22 PM

Correct. With a

_worker.js

_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

wrangler pages deployment tail --environment=preview

JJustinNoel Correct. With a `_worker.js` for toolsets like Remix, Astro, etc, you won't see ...

zwily•12/13/22, 12:07 AM

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

bkyerv•12/13/22, 5:10 AM

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

script

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

failed to parse url

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?

Unsmart•12/13/22, 5:27 AM

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

bkyerv•12/13/22, 5:56 AM

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

Unsmart•12/13/22, 6:05 AM

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

UUnsmart You can probably just remove the function all together and just fetch whatever d...

bkyerv•12/13/22, 6:11 AM

thank you. understood

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

JustinNoel•12/13/22, 4:17 PM

Not that I'm aware of. I added it to #pages-feature-suggestions

https://discord.com/channels/595317990191398933/920749372256419930/1052257731660230697

James•12/14/22, 12:12 AM

They are super cool, but I think that's very valid feedback. The process for node compat in Workers is as simple as adding

node_compat = true

node_compat = true

to your

wrangler.toml

wrangler.toml

. For a while, this worked in dev for Pages and not prod, and now it doesn't work in either. That's a pretty crummy DX and I think the Pages team is very aware of that.

There's work happening for Pages config where hopefully this kind of thing can happen, but I don't think there's any real ETA on that unfortunately. So ultimately, you're left to build a