move to pnpm

[vlkerag]

What does this change?

move from yarn to pnpm, ArtiomTr is preventing a move to a pnpm version >= 7: ArtiomTr/jest-coverage-report-action#406

Why?

pnpm is faster than yarn

Link to Trello

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4e4c367

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Deploy build 2054 of consent::cmp-monitoring to CODE

All deployment options

• Deploy build 2054 of consent::cmp-monitoring to CODE
• Deploy parts of build 2054 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[mxdvl]

I think you can use corepack which will enable PNPM without requiring consumer to install it directly, and use the packageManager to get a consistent version installed over time.

Here’s some example PRs moving to pnpm:

• yarn → pnpm dotcom-rendering#9476
• refactor(yarn): Try PNPM commercial#404
• Try out Astro.build guardian-engineering-site#125
• Use pnpm instead of yarn gateway#2196

And an ongoing discussion about moving to PNPM: guardian/csnx#445