Vi wasn't using any... turns out not importing it worked fine
V¯\_(ツ)_/¯
Vyes, so if my route is just a static asset and no worker could possibly be invoked, is that fine?
DI suppose so, in that case it would just be a static site i think
DI recommend using a framework to simplify this process. I use sveltekit, it has the cloudflare adapter which converts any server files you have into a worker.js folder without needing to really think about routes that much
Vwhy would i use a framework to handle literally 13 lines of code
Vthat's why i'm concerned- i only have one /functions/api/ route, and i don't want to be billed as if i'm using a framework
Dyou don't get billed extra for compiling it... using a framework can automatically create your
_headers _routes _worker.js _worker.js.map filesDsounds like your 13 lines of code could just be a turned into a regular cf worker? not a pages function so you can have more control over it
Vbut why do i need a _worker.js?
VI only have one file, and it’s not a worker.js- but the documentation is confusing on if i need to manually exclude it
Di dont have any experience with /functions/ files, _workers.js is 1 file that includes all the functions in 1 place.
Valright wonderful
EI know it's been a while but is there any update on this? I'm trying to use DO's in a sveltekit project, any info would be greatly appreciated
SI'm actually using flask frozen so at build time I have a python script that freezes my website.
SKinda weird, but I'm way faster in python that JS 
DI also wish we had the performance improvements of running lightweight python frameworks
Sare there any known issues with functions right now? We are getting 500s trying to use our function to upload to Cloudflare Images
JThere’s a known issue right now with various APIs throwing 500s. It’s being investigated and a fix should be out soon. Sorry for any inconvenience.
SFor once it isn't me! 
EA note was added to https://www.cloudflarestatus.com/incidents/03vm5mx76pc6
Cloudflare API in Pages Functions may also have been affected returning intermittent 500 errors.Thanks for the report @simpson2
A fix has been implemented and we are monitoring the results.
Ram trying to deploy Pages Functions on cloudflare but its not uploading functions folder at root project using wrangle cli
I have followed all steps mention in doc but still Pages functions not working Please guide me what I am doing wrong
I have followed all steps mention in doc but still Pages functions not working Please guide me what I am doing wrong
Ris their any additional configuration need to make Pages function work?
CSay I have a project with a directory structure like this, how can I:
- Share a module between them? Should I place it inside
functions/, and if so, will it become a route? - Import something from outside
functions/? Say I haveweb/src/utils.ts, can I import that from a function?
HEither way is fine. As long as you import it correctly, and wrangler can find it, it will build
IIs Workers Image Resizing supposed to work in Pages Functions? Like this example code? It seems to just ignore the
fetchUsing Image Resizing with Workers gives you powerful programmatic control over every image request.
KI don't believe it works
KFunctions aren't 'recognised' as running on your zone that has Image Resizing.
Ihell's bells. Well, that's one way to waste an afternoon
IIt works fine with /cdn-cgi/image URLs but ultimately I need the watermark/overlay feature which only works with the Workers method
JYeah you'll probably want to expose a Worker on a zone with Image Resizing or something
IYep. Silly me, thinking a custom domain on a Pages project would do the same thing 
CAnd this works with the Pages CI too, using the filesystem routing?
HYup, as long as you configure Pages to clone the right directory(so that the external import isn’t cut out), then it should build like normal
CWhat do you mean by the right directory? The root directory?
CAnd if I have a file at
functions/utils.ts, will that automatically become a route too, or does it need a onRequestonRequestGet/Post/etc to become a route (which becomes listed in _routes.jsonYes, as long as your root directory contains all of the code you import.
HIt will not. Routes are only generated when an
onRequest* export is presentCPerfect, thank you very much!
SHey all, been having some trouble trying to get up R2 + worker + image resize. The images are in the R2 bucket and are accessible through an existing worker (worker1). Another worker has been created with a route configured to /images/*.
Took the code from this https://developers.cloudflare.com/images/image-resizing/resize-with-workers/#an-example-worker and deployed the worker. When I try to access the worker (ie: example.com/images?image=https://worker1.com/cat.png), I'm hit with this
Took the code from this https://developers.cloudflare.com/images/image-resizing/resize-with-workers/#an-example-worker and deployed the worker. When I try to access the worker (ie: example.com/images?image=https://worker1.com/cat.png), I'm hit with this
Using Image Resizing with Workers gives you powerful programmatic control over every image request.
SAny suggestions on what I'm probably doing wrong here?
BHey functions team, I'm trying to deploy a simple hello world function. I am using nuxt.js and juxt content. I run it locally, no problem:
However, when I perform my deploy and then navigate to the page on the service, (it deploys and builds fine) but I just get a 404 .
it's the 404 provided by the framework (
npx wrangler pages dev -- npm run dev http://127.0.0.1:8788/helloworld = "Hello World"However, when I perform my deploy and then navigate to the page on the service, (it deploys and builds fine) but I just get a 404 .
it's the 404 provided by the framework (
nuxt.js) and i don't know how to override this / configure it to point to the pages function.