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