Upgrade Yarn 3.2.1 to 4.0.0-rc.9+

[leotm]

Only issue in Linux CI, macOS 13b locally is fine

Latest checked: rc.14

Ubuntu2204 (20220605.1)

yarn install

➤ YN0000: ┌ Resolution step
➤ YN0078: │ Invalid resolution node-forge@npm:^0.10.0 → npm:1.2.1 (yarn why: ... RN Flipper)
➤ YN0000: └ Completed
➤ YN0000: Failed with errors in 0s 137ms

• revert yarn.lock (v4 -> v3)
• revert (old v3) resolution commit
• yarn install (regen v4 lockfile)

yarn --check-resolutions
➤ YN0000: ┌ Resolution step
➤ YN0078: │ Invalid resolution prismjs@npm:~1.17.0 → npm:1.26.0 (yarn why: ... @storybook)
➤ YN0000: └ Completed
➤ YN0000: Failed with errors in 0s 137ms

• repeat

Similar on macOS Monterey 12.5 Beta

• doesn't block yarn install
• detected via yarn --check-resolutions

---

Next step

• Implements --check-resolutions yarnpkg/berry#4302 (comment)
• delete lockfile -> install v4?

---

Follow-up

• Upgrade Yarn from v3 berry to v4 canary rc.14 #846

Still need to undo resolutions

---

Close: #671

[leotm]

Check

• feat(patch)!: Improves patches yarnpkg/berry#4218
• Implements --check-resolutions yarnpkg/berry#4302
  • showing up on macOS too
  • but no install blocker

[leotm]

Yarn 4.0.0-rc.9 --check-resolutions (can't check in v3) recognising all prev/old v3 (manual) set resolutions Invalid

yarn set version canary
yarn install

yarn --check-resolutions
➤ YN0000: ┌ Resolution step
➤ YN0078: │ Invalid resolution node-forge@npm:^0.10.0 → npm:1.2.1 (yarn why: ... RN Flipper)
➤ YN0000: └ Completed
➤ YN0000: Failed with errors in 0s 137ms

revert yarn.lock (v4 -> v3)

revert (old v3) resolution commit

yarn install (regen v4 lockfile)

yarn --check-resolutions
➤ YN0000: ┌ Resolution step
➤ YN0078: │ Invalid resolution prismjs@npm:~1.17.0 → npm:1.26.0 (yarn why: ... @storybook)
➤ YN0000: └ Completed
➤ YN0000: Failed with errors in 0s 137ms

yarn install blocker on Ubuntu, not on macOS but still detected

[leotm]

yarn patch --revert-all --dev-deps needed 😅 or yarn reset resolutions -D or lockfile codemod

edit: ok only few

• 5bc69b5
• 3f40bbe
• 447031e
• a04b501
• f435cd0

shouldn't be necessary to upg Yarn v3 -> v4 🤔

temp: revert commits in order

solution: difficult w/o commit hist since lockfile snapshot overwritten 5x

hack: delete yarn lockfile to remove Yarn v3 resolutions, then re-create with Yarn v4? but resolutions lost on devDeps

[leotm]

follow-up attempt here: #846

[leotm]

Raised in

• Yarn 4 RC #1181

Followed up in

• Upgrade Yarn to v4.0.0-rc.32, refactor storybook and update jest mocks #1205