Same boat as you, I waited for the preview build to complete, it did, merged in prod and it failed.
Same boat as you, I waited for the preview build to complete, it did, merged in prod and it failed.
IIYeah, it's in the build image... they depend on that for some reason even if not required.
ILet's not get into updates to the build image, I remind them too much already 
W
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.lock if you really want to deploy.IIf 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?
