and also.... can't get it to work w/ local dev... which i can only imagine isn't supported? maybe t
and also.... can't get it to work w/ local dev... which i can only imagine isn't supported? maybe that should be in the doc?
CLocal dev is only supported. You can't do remote dev with pages
https://developers.cloudflare.com/pages/platform/functions/local-development/
https://developers.cloudflare.com/pages/platform/functions/local-development/
Run your Pages application locally with our Wrangler Command Line Interface (CLI).
Ayea, i'm talking about pages functions
CFunctions work in local dev
Awell i suppose i wish i had some better documentation to help me figure out why mine won't 
CWhat errors are you getting?
Ai have a public directory in my repo... for messing around i follow the hello world in the getting started... put the
functionshelloworld.jsnpx wrangler pages dev public/helloworldFunctions directory needs be at the same level as
publicthat did it, thank you
AIs it possible to get more updated pnpm? My project was failing to build earlier due to one of my packages requiring a more updated version of pnpm.
VHello everyone! I would like tell about a problem I am facing. I have a folder of icons of various sizes in a react project. I have deployed it to cloudflare pages. Now I have changed the icons without changing the file name and I see that the icons have been updated in the page opened through url cloudflare generated but not in the page with custom domain url. Changing all those file names is tedious, can anyone help me on how to overcome this?
DHi! Did you set up caching for that custom domain? If so, you can remove it (and do a manual purge), Pages has internal caching that makes enabling cache rules redundant for assets hosted with Pages
VThank you Dani, I will check it!
VHow long can it take? I thought that about 30 seconds are enough after purging, but I cannot see any changes after deploying the new build. When I access the assets through the path from custom domain, I am able to see the latest assets, but when I look at manifest, they are the same old icons.
CDoes Pages build store built app in a git repository? 
KNope
Cwouldn't that help reduce storage usage?
ESorry about that, this is something that the Pages team are aware of and are planning to improve on. In the meantime we created this guide on things to look out for, including CAA records https://developers.cloudflare.com/pages/platform/debugging-pages/
Iseemed to have started running into this
IGuessing it's a cloudflare side problem? pages-helpFailing deploy (Could not generate the asset manifest)
ZWe're raising it with the team! Thank you for reporting it
IThanks
TSame Error for me
IIssue on their end, theyre working on it
DOK thanks!
IThe one time I wake up early to experiment with some deployments…
Care we practicing GitHub methodology? 
MSame error here...
IThere is an incident declared, follow the status page posted just above
MThank you! I'm following it
DIt's working now. Thanks for the quick responses and fix 
CYou're welcome 
. Thank to the team, not me.
. Thank to the team, not me.
ZPlease don't imply that you're an employee
CEThat's an issue on the side of node, it shouldnt happen if you switch to Pages build system v2 and set a major version for node e.g.
NODE_VERSION=16Since v2 will prepackage the latest of each major version
CI didn't notice. Now I removed
NODE_VERSION=16
EHm getting this myself weirdly
E
PIs there any way to see why a pages deployment failed? Wrangler doesn't give any errors, but the page is stuck on deployment not found and when I go to the dashboard it says deployment failed. It is probably just an issue with my code because deploying an earlier version of it works, but idk how to find what went wrong because usually when there is a problem either wrangler will catch it or it will still deploy but the function will give an error.
E?pages-deployment-id
FThe Pages deployment ID is a unique build identifier.
It's the UUID in the browser bar (for example, a URL would be
This ID can help troubleshoot some issues with Pages builds so if you have a failing build make sure you grab that ID for the Pages team to use.
It's the UUID in the browser bar (for example, a URL would be
dash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT/DEPLOYMENT_IDThis ID can help troubleshoot some issues with Pages builds so if you have a failing build make sure you grab that ID for the Pages team to use.
EThere are some errors that are not made visible to the user for one reason or another - If you have this deployment ID, someone from Cloudflare can check it for you
UWhat happens when you run the script?
POk, thank you for the information. It was a silly mistake I was able to figure out myself, I was just missing a couple commas. Though it is strange that wrangler didn't let me know because usually it detects stuff like that.
