II alerted the Yarn admins, not fixed yet though.
IILuckily it's Sunday.
ISame.
IYeah, I tried both channels, one seems to have gone to the admin, but he pinged a maintainer who hasn't replied yet.
IYou need to remove the
yarn.lockIf that's in there, it will try to install yarn.
IYarn has clicked "renew" on their Netlify certificate, so it's now fixed! 
IITook them long enough to check Netlify, after blaming Cloudflare in a message and then realising it wasn't proxied by Cloudflare when I told them 
IWhen I read Cloudflare, I checked if it was, as I could reach some people in that company
IBut not CF's fault this time.
I
DA couple of months ago, I tried to host a NextJS application on Pages, using their Edge Runtime, but kept running into errors and issues. Is anyone having good luck recently hosting NextJS on Pages?
SHas anyone had success with Remix Run And D1? The documentation is very limited.
Jhow does using cloudflare pages in advanced mode compare with using workers sites? the former costs $20/m and the latter costs $5/m? but pages gives you unlimited requests?
Jdoes that make workers sites more appropriate if you have lower traffic?
Jis cloudflare pages basically just a worker, with some automatic static resource stuff and a different pricing model?
KI have a pages project connected to my gitlab project. I accidentally deleted the webhook in my gitlab project when removing another webhook and, well it is now gone.
Is there anyway to get the pages project to recreate the webhook?
Is there anyway to get the pages project to recreate the webhook?
JFor argument sake say I'm hosting a remix site, I still don't see one being more suitable than the other
SYou would use Pages.
Jfor both of them I would define a worker that handles any request and passes it to the relevant function for the framework
SAs you can can build a deployment pipeline through Github et al.