K
CIt's running 
Cbut I get 404...
CAlready tried all of those.
C/cc @kian | DevDocs 
CStill happening even after I updated to
2.6.2...
CSkye helped me in the DMs (so I could share my file).
Wanted to leave a note here.
Thanks!
Wanted to leave a note here.
Thanks!
JCorrect. With a
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:
_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
ZIs there any plan to fix this? Been that way for a long time and it seems like a bug
BI 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?
UYes that's normal. Functions are only available when deployed.
Band if I want to fetch data during build I would need to set up a full scale worker?
UYou can probably just remove the function all together and just fetch whatever data you need in the astro component. 
Bthank you. understood
JNot that I'm aware of. I added it to #pages-feature-suggestions
https://discord.com/channels/595317990191398933/920749372256419930/1052257731660230697
https://discord.com/channels/595317990191398933/920749372256419930/1052257731660230697
JThey are super cool, but I think that's very valid feedback. The process for node compat in Workers is as simple as adding
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
node_compat = true to your 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
_worker.js yourself if you need to do anything complex JFunctions has an "advanced mode" where you can effectively just run a Worker, and then get assets via
env.ASSETS: https://developers.cloudflare.com/pages/platform/functions/advanced-mode/JThis will mean that every call to your site will count towards your limits though - static assets are no longer free unless you configure your
_routes.json: https://developers.cloudflare.com/pages/platform/functions/routing/#creating-a-_routesjson-file
JCI, GitHub integration, and easy static assets
Upreviews
Ubiggest one imo
JWouldnāt that be cool 
HYou need the Cloudflare Response type. I recommend setting workers-types as a global type package
HShould look something like this: https://raw.githubusercontent.com/mrbbot/slshx-starter/master/tsconfig.json
HNo problem!
IHi! Is it possible to have a websocket server inside a pages function, or does this require a separate worker?
IAh amazing! Will give it a try, thanks (: