�@jsk
Jyeah I wouldn't overlap utility funcs names w/ onRequest but I think as long as say /functions/util.js or /functions/googleOauth.js isn't treated as an api endpoint on my actual cf pages site exporting functions like:
export function getTime() {
...
}
export function getGoogleOauthToken() {
..
}
Then it should be fine.
I think this ties into wrangler and esbuild in some way but im not really sure since its not documented for cf functions how the functions are built, ie: the treatment of utility and helper methods in the /functions dir
I also think this relates somewhat to 'npx wrangler pages functions build' to see what the actual build file being deployed actually is, how its compiled but im not certain about that either lol
Thanks for the input/feedback anyways @[@] ��������������.
export function getTime() {
...
}
export function getGoogleOauthToken() {
..
}
Then it should be fine.
I think this ties into wrangler and esbuild in some way but im not really sure since its not documented for cf functions how the functions are built, ie: the treatment of utility and helper methods in the /functions dir
I also think this relates somewhat to 'npx wrangler pages functions build' to see what the actual build file being deployed actually is, how its compiled but im not certain about that either lol
Thanks for the input/feedback anyways @[@] ��������������.
�You're welcome, happy to help.
JIn the future, to help anybody struggling with similar questions, I've compiled some useful info below w/ citations that is ~correct!
Am open to corrections if there is a mistake in understanding
1) All .js/.ts files inside of the /functions dir is automatically bundled together on pages build/deploy into a single _worker file.
SOURCE: https://community.cloudflare.com/t/cloudflare-pages-functions-bundled-or-not/577646
2) All .js/.ts files inside of /functions that:
So this means if you have files like /functions/utils/*.ts, and do not export any onRequest handler inside of them --
But do use that code in your actual api endpoints, cf should bundle your functions code into a single file as expected on build/deploy
(ex. npx wrangler pages dev out/ or npx wrangler pages publish out/) --
Without ending up with api endpoints for utility modules like /functions/utils/helper.js
Can test this as well on dev/prod and make sure you end up with 404's for those endpoints + no functions usage.
SOURCE:
functions
functions
3) Because the /functions code is being bundled and generated into a single _worker file, imports from outside of the /functions directory may actually work
correctly in the final bundled file, as long as cf can find the code to bundle together, like from say '../utils/helper.js' as per:
SOURCE: functions
4) I believe CF functions are bundled together using esbuild during build/deploy but I am not sure about this. Extrapolating from https://developers.cloudflare.com/workers/wrangler/bundling/
Am open to corrections if there is a mistake in understanding
1) All .js/.ts files inside of the /functions dir is automatically bundled together on pages build/deploy into a single _worker file.
SOURCE: https://community.cloudflare.com/t/cloudflare-pages-functions-bundled-or-not/577646
2) All .js/.ts files inside of /functions that:
- do NOT export any onRequest* handler
- are imported into modules that DO export a onRequest* handler
So this means if you have files like /functions/utils/*.ts, and do not export any onRequest handler inside of them --
But do use that code in your actual api endpoints, cf should bundle your functions code into a single file as expected on build/deploy
(ex. npx wrangler pages dev out/ or npx wrangler pages publish out/) --
Without ending up with api endpoints for utility modules like /functions/utils/helper.js
Can test this as well on dev/prod and make sure you end up with 404's for those endpoints + no functions usage.
SOURCE:
functions
functions
3) Because the /functions code is being bundled and generated into a single _worker file, imports from outside of the /functions directory may actually work
correctly in the final bundled file, as long as cf can find the code to bundle together, like from say '../utils/helper.js' as per:
SOURCE: functions
4) I believe CF functions are bundled together using esbuild during build/deploy but I am not sure about this. Extrapolating from https://developers.cloudflare.com/workers/wrangler/bundling/
AI have a function that should trap /u//api requests and bypass anything else under /u.
```js
export function onRequest(context) {
var url = new URL(context.request.url);
if (pathname.match(//u/(\d+)/api./)) {
// proxy this works
}
return fetch(request); // this doesn't throws 500
}
```
How should i make original request that I don't want to modify from function? I tried
return fetch(request);
return fetch(request.url, request);
Neither works. Any insight would help. Thank you.
```js
export function onRequest(context) {
var url = new URL(context.request.url);
if (pathname.match(//u/(\d+)/api./)) {
// proxy this works
}
return fetch(request); // this doesn't throws 500
}
```
How should i make original request that I don't want to modify from function? I tried
return fetch(request);
return fetch(request.url, request);
Neither works. Any insight would help. Thank you.
�I don't know if it'll work but I don't even think you should just return a literal fetch
IThis won't pass headers. The fetch with the full request should work, are you seeing anything in the Pages log tail?
�No no, I was replying to the person above
IYeah, I was following up on what you said. The person above's original method should work, by doing it the way you are no headers are going to be passed from the request.
KHi, anyone ever success creating a integration between cloudflare websocket hibernation (durable object) with the cloudflare pages function? I got error when doing binding in local
�Ah well then, I beg your pardon, I have just started using cloudflare for about a month now so I'm still a bit new to all of this.
INo worries, just wanted to point that out
IPages Functions can't define Durable Objects, you'd need to define the DO in a Worker and deploy it first
Kits defined in https://developers.cloudflare.com/pages/functions/wrangler-configuration/#durable-objects
does it not working?
does it not working?
Cloudflare Docs
Pages Functions can be configured two ways, either via the Cloudflare dashboard 
or wrangler.toml, a configuration file used to customize the development and deployment setup for Workers and Pages Functions.
or wrangler.toml, a configuration file used to customize the development and deployment setup for Workers and Pages Functions.IYou must create a Durable Object Worker and bind it to your Pages project using the Cloudflare dashboard or your Pages project's wrangler.toml. You cannot create and deploy a Durable Object within a Pages project.It needs to be already defined/created in a Worker.
Kso we need 2 separate deployment / wrangler.toml ya? one for the workers and the other for the pages?
IYeah. You need to deploy the Worker with the DO first, then the Pages project after the DO is deployed.
KIf somehow I want to connect internally both of them using D1 does that possible, how to configure the wrangler toml? and on local developments?
KThanks for this comment. It's not in the docs here (I guess it is in video, actually) https://developers.cloudflare.com/pages/framework-guides/deploy-an-astro-site
CHey, does anyone know if it is possible to cache the response of a page function? I have a middleware function that modifies the meta tags for a dynamic route, but I don't want that function to be invoked everytime a request is made to it (it will be returning the same response everytime for a given path (username)).
HYou can generate them at build time, if that is what you mean?
CWell it’s a dynamic route not a pre-rendered one
CBut for a given dynamic route it would be awesome to cache the page function response if possible
HYou can cache return values, but the Worker is still invoked
EHi, I have a problem with a custom domain and astro5 actions. The default domain ( pages.dev) works well (show the last version), but the custom domain fail with the actions, and I have to refresh (F5) every time
EIs the cache of custom domain diferent to the default domain ?
Khi does it possible, to run a cloudflare pages function, and the function itself is websocket hibernation api?
any simple example to do it? if anyone knows?
any simple example to do it? if anyone knows?
HIt can be? Do you have any cache rules on your custom domain?
HYou would need to deploy a Worker separately, which declares a Durable Object
Bis there any plans for firebase sdk support on functions?
MHey guys, I've tried searching for the solution but no luck -- i simply want to cache the json response of a certain cf pages function using the cache-control header -- the cache works on the browser level, however in the response headers there's no trace of cf cache
I have query parameters, might that be the issue? hoping for someone who's done this recently and is familiar with the issue
I have query parameters, might that be the issue? hoping for someone who's done this recently and is familiar with the issue
HAre you calling the cache API?
EI have already found the solution. The problem was that "Rocket Loader" was activated.
Thanks
Thanks
Chi yall, is this a place i can ask questions about the verification process for cloudflare? im trying to log into a site and im not getting any option to check. see the screenshot of the page and the dev console. Using brave
E#general-help
WHi, having some problems deploying a remix SSR site via github actions? Anyone live who can help me out or direct me to some documentation?
THas anyone cleaned up their functions logging, so it only returns the information you want as far as the header response? Or is that something only workers can do?
For example, id love my functions to process traffic logs and purge stuff like this in some cases >
For example, id love my functions to process traffic logs and purge stuff like this in some cases >
RProabaly asked a 100 times, but here it goes : Can i push a pages function on its own without deploying to github first? -- I know i can create a new work and push that seperately, but the domain and route isn't the same...cumbersome to push entire repo for 1 function update no?
HSure, you can use
wrangler to perform a direct uploadRin this case, what will the url be to call the function ? usually i would call /api/function
HWhatever the URL you set? The setup for creating the function is exactly the same, just instead of running
git push to deploy, you do wrangler pages deployRAh so i create the function as i would in the functions dir, then dploy it using wrangler pages deploy <BUILD_OUTPUT_DIRECTORY> [OPTIONS] .
I would still need to build the repo though client side, -- can i only deploy the function itself not the whole package, so that cf pages doesn't have to rebuild. it.
I would still need to build the repo though client side, -- can i only deploy the function itself not the whole package, so that cf pages doesn't have to rebuild. it.
HDirect Upload via
wrangler assumes you have already performed a build, it doesn't do anything(other than Functions bundling when using the functions directory) other than uploading.ROkay great thank you much! --
RAnyway to use a function to allow custom domains for my app? i.e. docs.mycustomer.com -> mypage.pages.dev -- I am using custom domains but on pro i am approaching the hard limit of 250... we dont charge our charities/ngos for this, wonder if i can continue to offer this service or i need to kill it... k
Rvanity domains.
HFunctions wouldn't do anything here, at least if I understand what you are trying to do. Have you considered using Workers Assets instead of Pages? Then you can run CF-for-SaaS yourself, and have more control
Cloudflare Docs
Create full-stack applications deployed to Cloudflare Workers.
RSeems like my framework Vue isn't support as it as SPA vs a Server side framework like nuxt/next --- In anycase, even if i were to use static assets, and run cf-for-saas wouldn't i still be limited to the hard limit of 250 for a pro account? -- on a seperate note i did fill int he form to request for a higher limit, have not heard back as of yet....
HYou should be able to get up to 5k iirc by paying
Rwhen deploying only the new functionn i made in the /function folder, using wrangler pages deploy ./disst it will deploy the entire projet, i dont wnat to do that i only want to deploy the new function i created