Unknown error causing CF Pages to Error out during building application
Original message was deleted
S
JI'm getting this also, did you find a solution?
W2024-02-08T01:46:22.721881Z ➤ YN0070: Migrating from Yarn 1; automatically enabling the compatibility node-modules linker
2024-02-08T01:46:27.590526Z ➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
v2 build image defaults to Yarn 3 not Yarn 1. Add an env var
YARN_VERSION with the value 1JYep, I found your earlier message from 4/18 and this is the fix. Thank you @Walshy | Deploying
JIt may be worth noting, we didn't have issues with this before, we had v1 specified in the package.json as
"packageManager": "yarn@1.22.19", unless maybe a cutover just happened to v2 in the last weekJOr perhaps we changed the compat date and didn't notice this
Wno projects have been migrated to v2 and compat date doesn't impact it. You explicitly need to select v2 in the UI. New projects default to v2 but old ones are still v1 unless manually moved.
JThanks, yeah, we've been on v2 the whole time. We are unblocked and don't need help anymore, but if you do want to investigate, here are 2 deploys 6 hours apart, with same yarn lock file, both complaining about node-gyp but one build finishes and passes, and the other fails. Neither had the YARN_VERSION=1 change
Pass: 08a64c0c-f878-49dd-8b1c-832724dc82e5
Fail: e750d656-a257-42a6-95ba-91667773f4b9
I did add YARN_VERSION=1 after the fail and reading discord, and it now passes: adb443c3-ec2f-4e79-af58-6c6cca5b8340
Pass: 08a64c0c-f878-49dd-8b1c-832724dc82e5
Fail: e750d656-a257-42a6-95ba-91667773f4b9
I did add YARN_VERSION=1 after the fail and reading discord, and it now passes: adb443c3-ec2f-4e79-af58-6c6cca5b8340
