And yeah, the second one is right there because the param passed to onRequest is a context not a req
And yeah, the second one is right there because the param passed to onRequest is a context not a req, env like in normal Workers
W
NAh, thanks, I can go sleep now 
MI was wondering if
It's not stated explicitly , but I read it is not in normal standalone Workers, that's why I'm asking.
Same for using TypeScript in Advanced mode, having a
Don't want to use in in a way that later might break...
_routes.json (https://developers.cloudflare.com/pages/functions/routing/#create-a-_routesjson-file) is supported in Functions Advanced mode ?It's not stated explicitly , but I read it is not in normal standalone Workers, that's why I'm asking.
Same for using TypeScript in Advanced mode, having a
./_worker.js folder with a index.ts seems to be automatically transpiled and it works. But is this expected behavior?Don't want to use in in a way that later might break...
HYes & Yes
Mthx for confirming 
VWhen Pages Function is faces an issue of getting a response from the external endpoint, it throws 500 Internal error which basically crashes my frontend. How can I capture this error and throw an appropriate error response to handle in my frontend?
when I try to fetch from the endpoint, I can't even get a res to do that. Or is there a way and I am missing something?
when I try to fetch from the endpoint, I can't even get a res to do that. Or is there a way and I am missing something?
II see that the -- and proxy options have been deprecated, but I cant find an alternative. Im using Vite and want the hot module refresh. If i jsut use a ./dist directory that wont happen...
IAre you wanting to capture the status code in your frontent, or are you using the function as middleware and want to just pass through to the static assets if the function fails?
IAlso, are you calling an API from within the function, and when the fetch fails for any reason (non 200 status) you want to return a specific error message from your function, and is automatically displayed on the front end?
HAfaik the recommendation is to use a framework that supports dev bindings: https://blog.cloudflare.com/blazing-fast-development-with-full-stack-frameworks-and-cloudflare
The Cloudflare Blog
You can now use your framework’s development server while accessing D1 databases, R2 object stores, AI models, and more. Iterate locally in milliseconds to build sophisticated web apps that run on Cloudflare
IDoes this work with React with Vite as the build tool? Sorry if I missed it on there
IOh nvm I found it. Looks like it does. Thank you, I will try that out.
VYes, when theres a 500 internal error it can't send a response.
I am fetching from the function and returning some data. but when the source is not reachable, the function does not send anything. For now I am handling such kind of crashes on my frontend with a blanket error, so not knowing why it failed.
I am fetching from the function and returning some data. but when the source is not reachable, the function does not send anything. For now I am handling such kind of crashes on my frontend with a blanket error, so not knowing why it failed.
VI know not an ideal solution but when using functions I let wrangler do its thing to run the function with the ./dist but I also run a the vite server for my frontend on its own. And access the :5173 instead of the :87xx by wrangler.
This way when using the functions it uses the wrangler's endpoint to get the data but otherwise I take advantage of Vite's HMR for the frontend.
I am not sure how this will work for other CF services run through wrangler.
This way when using the functions it uses the wrangler's endpoint to get the data but otherwise I take advantage of Vite's HMR for the frontend.
I am not sure how this will work for other CF services run through wrangler.
HYou need a Worker to export the DO
HAs for RPC, it should work
II thought about that but won’t the frontend try to use the 5173 port when fetching data, or do just just manually specify the 8788 port for all fetch’s?
Vyes manually specify it. using a .env.local file as a proxy of sorts in development. its cumbersome but works.
ISo when the api you are calling from within the function is offline, it fails to fetch, and the worker is just returning 500 because the response never exists.
If this is the case then I think you can use a .catch() after the fetch and put a callback that returns whatever error you want your function to return when that happens.
If this is the case then I think you can use a .catch() after the fetch and put a callback that returns whatever error you want your function to return when that happens.
IIn a .then() (or if using await) then you can do basically the same with the status codes.
VThanks for still thinking about it. Unfortunately, that doesn't work or not at least locally.
It does not return anything as the fetch never completes, so the function just shows 500 internal error on the server but doesn't execute any further. I tried shortcircuit with datares.status to check for 500 but it doesn't work that way as by that time the function errors out and not the origin server (for which datares checks for).
The 500 error is the function error but nothing is checking for the function error itself.
I am not sure if I am explaining it well.
I found out this, apparently the 500 error will only be returned if its timeout by due to DNS error https://community.cloudflare.com/t/community-tip-fixing-error-500-internal-server-error/44453 but other reasons it will not return anything like in my case where the origin server does not respond. The linked docs page in that article seems helpful for all the possible CF error codes
It does not return anything as the fetch never completes, so the function just shows 500 internal error on the server but doesn't execute any further. I tried shortcircuit with datares.status to check for 500 but it doesn't work that way as by that time the function errors out and not the origin server (for which datares checks for).
The 500 error is the function error but nothing is checking for the function error itself.
I am not sure if I am explaining it well.
I found out this, apparently the 500 error will only be returned if its timeout by due to DNS error https://community.cloudflare.com/t/community-tip-fixing-error-500-internal-server-error/44453 but other reasons it will not return anything like in my case where the origin server does not respond. The linked docs page in that article seems helpful for all the possible CF error codes
ISorry but im still not sure I’m understanding.
IMaybe you could share some code around this spot?
Khello everyone where can i ask about cloudflare calls beta about inactivity calls to disconnect as i cannot find any snippet code to do this
E#stream
PIs there some authentication support for Functions? what I've seen for Okta seems to require express
ILucia Auth library supports functions I think, though it definitely requires more work on your end than a paid solution
Sdoes cloudflare offer a way to run a nest.js backend serverless to conenct to like a gitlab (i was thinking of doing vercel but i like whats in CF capabilitys
AI have created a pages function with following code in a file called index.js and put it directly under the functions folder -
The idea behind this function is to execute it before serving index.html file ONLY and to avoid it for other static assets from pages application. This is something which I could not achieve with worker or functions middleware. While this works in local setup, this is not getting executed when deployed on cloudflare. So my question is which behavior (local or cloudflare) is correct?
The idea behind this function is to execute it before serving index.html file ONLY and to avoid it for other static assets from pages application. This is something which I could not achieve with worker or functions middleware. While this works in local setup, this is not getting executed when deployed on cloudflare. So my question is which behavior (local or cloudflare) is correct?
HIt should just work? Just published https://functest.pages.dev/ to test, and only the index should have the header
functions: wuz hereWelcome to my website!
ACan you try this with a custom domain and see if it is working? If yes then I will create a simple pages project tomorrow and test it again.
HWelcome to my website!
AThanks. Will test it again and see if something is wrong on my side.
ACan you share the code of your pages function? Did you make any other change to your pages functions application to make it work?
DDoes Functions support logpush?
RIs having an "exclusively" function (worker) backed Pages project without a SPA in front considered an anti-pattern and would eventually bite me?
I guess that having a SPA in front might be cheaper to run, since not every request will trigger a worker invocation, but it could be more expensive (slower) to develop without enough experience with the selected SPA framework
I guess that having a SPA in front might be cheaper to run, since not every request will trigger a worker invocation, but it could be more expensive (slower) to develop without enough experience with the selected SPA framework
AI tested it with a simple functions application today and it is working as expected. I need to figure out why it is not working for my other application. Thank you for looking into it.
B@HardlyWorkin' I have an issue with my Cloudflare Functions. I followed the steps to create a Cloudflare Pages project with Functions using the
I created a new function named
When I tried to test my function locally using
wrangler pages project create command, but I'm encountering problems when trying to access my functions.I created a new function named
hello.js inside the functionsWhen I tried to test my function locally using
npx wrangler pages dev ./, I couldn't access it at http://localhost:8788/hello. Additionally, after deploying my project to Cloudflare Pages, I attempted to access my function at https://<my-project-name>.pages.dev/hello, but it didn't work either.
HTry putting your assets in a subdirectory
