All right, that makes sense, too bad workers doesn't have the nice GitHub-integration that pages has
All right, that makes sense, too bad workers doesn't have the nice GitHub-integration that pages has
DIt kind of does though, if you work on it locally you can deploy the worker with wrangler and I believe it will use the commit description that you last used on it. You can also then go to the dashboard and see that history and rollback to whatever deployment you had
TSure and that works well for a single dev, but if I had multiple people working on it and perhaps mulitple workers (I'm currently looking at having just one for now and do routing) I'd prefer everyone not having to deploy from their machines 
TBut it's a minor thing really, for now I just want to get more clarity on when to use what
DApparently from what I've learnt it's ok to have 1 worker containing everything you need since it only really affects cold start times, and as long as it's warm it should be instant I think
DJust make sure any new npm packages don't bloat your worker, I had some random packages I didn't even use much load entire 7MB json files into the worker
TThe dangers of npm, I'm a frequent user of bundlephobia.com for that reason
Acould be a compression issue
Aim having a similar sort of problem with a specific deployment of my site, but every other deployment is fine
AI have not managed to fix it
Ait seems to only happen on my own network which is weird
JI'm going to escalate this for you - we've seen this happening quite a bit recently.
JThanks Matt
YHi , i am trying to run pages functions locally and getting error "ā [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above." Wrangler is compiling the pages function to worker successfully . My env is Ubuntu 23.04 + node v20.5.1 + npm 10.0.0 +Vite - React . Am i missing something ?
SIf you load an SSR page that has 20 static assets (jpgs, etc...) does every time that page loads for a new user get counted as 21 function invocations against your total (page + all assets) as seen in the real-time logs?
HIt depends on how good you/your framework is at generating a _routes.json. If done correctly, you could do it in a single Functions request
Si'm using next-on-pages, I don't think it generates a _routes.json file
Sis there documentation on _routes.json?
HOh yeah, I remember chatting with one of the people that works on NOP, and they said something along the lines of implementing _routes.json might break how Nextās routing works, even for static assets
HFunctions utilize file-based routing. Your /functions directory structure determines the designated routes that your Functions will run on. You can ā¦
JYeah so I secretly added support for
_routes.jsonI moved all of our static assets within our public folder to a new subfolder and added a wildcard pattern (/static/*) and so far it seems to work perfect
Rhow would i install a npm dependency for a pages function? i.e stripe
Rcan find anywhere in the pages functions docs where i can install depdencies : https://developers.cloudflare.com/pages/platform/functions/local-development/
KSame as any other JS project
KInstall it with a package manager of choice & import it in your Functions files
EYeah, you can
E
ECorrect, it wont invoke the function for GETs if you do that
HIt does still bill you though, right?
HSince routes are by URL, not by method
R@kian in a /fuctions folders i have all the endpoints like helloworld.js, so im guessing your saying i npm ini the entire functions folder? and import xx from 'xxx' -- cf pages still says cannot find module xxx.
Rget this error when calling the stripe module :
