Pages Functions? No, not yet no. Certainly something they want to ship as soon as possible..
Pages Functions? No, not yet no. Certainly something they want to ship as soon as possible..
SCan someone handhold me with functions? I'm really confused with using Worker Docs for functions. I would love if someone can teach me (or link me to something) how to write a hello world in my already-deployed CF Pages project. I might be able to take it from there. Please please handhold me.
I2 questions there. The answers are:
- yes, you can, but you need to create the DO outside of Pages and use a
--bindingflag withwranglerfor now. - there's no Functions logs yet, but that will be solved by the time Functions are out of beta.
BHmm how should you do types for the functions?
Bnvm
EYes, but
ENo
EKeep in mind that you cant use the cache API from a workers.dev domain so the worker youre calling wont be able to cache anything
EThats about the only caveat, works fine otherwise
Kdo Functions have service bindings yet?
K
EI dont think so
Ethat would be the real solution if they did
KAlthough I think by the time that’s a thing, R2 bindings will probably be so too
Eif they were supported theyd show up here
Ebut they dont so theyre not
Ecalling the workers.dev is definitely the best solution for now :)
Kwrangler2's
wrangler pages dev is the only one that I'm aware ofKPages currently just inherits your highest zone so there's no specific Pages plan.
No idea about the burst limits.
The 100k/day is just whilst it's in beta & billing will likely be similar to the Bundled model on the Workers paid plan when in GA.
No idea about the burst limits.
The 100k/day is just whilst it's in beta & billing will likely be similar to the Bundled model on the Workers paid plan when in GA.
Kiirc Functions will be Bundled if you have a paid Workers plan - i.e 50ms CPU time
Kso I'd assume it inherits the increased burst limit
EWhat @kian said.. with the only other caveat that you can get your limit increased. There is a form for it somewhere, or DM me with what you want to use it for and what you would need and I can see if we can accommodate that
IGoogle Docs
If you have hit your limit for invocation requests while deploying your functions on Cloudflare Pages, you can submit this form to our team to learn more about your use case. Please provide the information below in case we need to chat with you more about raising the limit.
Please note: this limit increase is only applied to Functions deployed...
Please note: this limit increase is only applied to Functions deployed...
JAFAIK that’s still the case
Jbut if you’re running into limits you can use the form that’s pinned to this channel
RHey there! Quick question about Functions built with
I get a
Any body tried and achieve this using Pages Functions?
Thanks!
onRequestPost. I need to retrieve the header sent but nothing is mentioned on the Pages Functions doc... I tried applying the Workers doc suggestion but when I do so on Wrangler:I get a
Could not resolve "crypto"Any body tried and achieve this using Pages Functions?
Thanks!
ICrypto? That seems like a completely seperate issue from the code snippet you sent. Are you importing anything by chance?
ROh yeah... my IDE added a require in there. I can get the headers now using: 
const customHeader = await context.request.headers.get('my-custom-header') Thanks for your quick wits 
Awhere did you find it? I have a vitejs project and struggling to run functions locally
Ado you mind sharing your
wrangler.toml and vite.config.js? Been trying to get this to work for an embarrassing amount of timeAif anyone has any vitejs project that has Cludflare Functions integration please bless me with a link
A-the function
-the file in /functions/api
-wrangler cli:
-the request:
-the response
what am I doing wrong? '
-the file in /functions/api
-wrangler cli:
wrangler pages dev functions-the request:
http://127.0.0.1:8788/api/ping-the response
what am I doing wrong? '
A
Asorry don't mean to spam. Forgot to attach a screenshot
Athe pain is no more. I switched from default export to named export and it magically worked. I had the compiled file opened on the side and saw it was missing one API route. Updating the file with the missing route I noticed the compiled file does live update reflecting changes I make
Ai actually don't like default exports and rarely ever export default but this time I did and i'm never doing it again lol
EHaha.. 
Scan I look at a github repo with functions actually deployed? I wanna look at the directory structure etc
SPlease help me debug this hello world functions error. Logs in comment ->
SFinished
22:01:39.225
'wrangler pages <command>' is a beta command. Please report any issues to https://github.com/cloudflare/wrangler2/issues/new/choose
22:01:39.266 ✘ [ERROR] Transforming async functions to the configured target environment ("es5") is not supported yet
22:01:39.266
22:01:39.266 ../../../buildhome/repo/functions/api/hello.js:2:7:
22:01:39.267 2 │ export async function onRequestPost(request) {
22:01:39.267 ╵~
22:01:39.267
22:01:39.267 The target environment was set to "es5" here:
22:01:39.267
22:01:39.267 ../../../buildhome/repo/tsconfig.json:3:14:
22:01:39.267 3 │ "target": "es5",
22:01:39.267 ╵~
22:01:39.268
22:01:39.270
22:01:39.364 [31m✘ [41;31m[[41;97mERROR[41;31m][0m [1mBuild failed with 1 error:[0m
22:01:39.365
22:01:39.365 ../../../buildhome/repo/functions/api/hello.js:2:7: ERROR: Transforming async functions to the configured target environment ("es5") is not supported yet
22:01:39.365
22:01:39.365
22:01:39.365 [32mIf you think this is a bug then please create an issue at https://github.com/cloudflare/wrangler2/issues/new.[0m
22:01:39.377 Failed building Pages Functions from /functions.
22:01:40.224 Failed: an internal error occurred
22:01:39.225
'wrangler pages <command>' is a beta command. Please report any issues to https://github.com/cloudflare/wrangler2/issues/new/choose22:01:39.266 ✘ [ERROR] Transforming async functions to the configured target environment ("es5") is not supported yet
22:01:39.266
22:01:39.266 ../../../buildhome/repo/functions/api/hello.js:2:7:
22:01:39.267 2 │ export async function onRequestPost(request) {
22:01:39.267 ╵
22:01:39.267
22:01:39.267 The target environment was set to "es5" here:
22:01:39.267
22:01:39.267 ../../../buildhome/repo/tsconfig.json:3:14:
22:01:39.267 3 │ "target": "es5",
22:01:39.267 ╵
22:01:39.268
22:01:39.270
22:01:39.364 [31m✘ [41;31m[[41;97mERROR[41;31m][0m [1mBuild failed with 1 error:[0m
22:01:39.365
22:01:39.365 ../../../buildhome/repo/functions/api/hello.js:2:7: ERROR: Transforming async functions to the configured target environment ("es5") is not supported yet
22:01:39.365
22:01:39.365
22:01:39.365 [32mIf you think this is a bug then please create an issue at https://github.com/cloudflare/wrangler2/issues/new.[0m
22:01:39.377 Failed building Pages Functions from /functions.
22:01:40.224 Failed: an internal error occurred
Sis es6 ok?
Syeah es6 ok 
SThanks
SHere's an error on my console:
The function:
The frontend code:
GET https://mydomain.com/api/hello 404
Response {type: 'basic', url: 'https://mydomain.com/api/hello', redirected: false, status: 404, ok: false, …}
The function:
addEventListener('fetch', event => {
event.respondWith(handleRequest(event.request));
});
async function handleRequest(request) {
return new Response('Hello worker!');
}
The frontend code:
async function fetchMovies() {
const response = await fetch('/api/hello');
// waits until the request completes...
console.log(response);
}
fetchMovies();
SWhy the 404? I guess I'm missing something obvious?
JFunctions need to export things like
onRequestGet to handle requests: https://developers.cloudflare.com/pages/platform/functions/