chore: add the packageManager key generated by corepack to package.json

[cacieprins]

• Closes

Additional details

When yarn is run via corepack, it adds the packageManager field to package.json if it isn't already present. This adds that field, referencing the latest version of Yarn Classic (1.22.22).

Steps to test

How has the user experience changed?

PR Tasks

• [NA] Have tests been added/updated?
• [NA] has a PR for user-facing changes been opened in cypress-documentation?
• [NA] Have API changes been updated in the type definitions?

[MikeMcC399]

Are there any additional considerations for setting up a clone of Cypress due to this change?

If yes, they should be added to CONTRIBUTING.md.

You might want to mention:

corepack enable yarn

and the fact that corepack is experimental.

[MikeMcC399]

corepack is marked with Stability: 1 - Experimental with the text "Use of the feature is not recommended in production environments."

• Quite a while back (Sep 2023) I added it to feat: set yarn classic for corepack enabled cypress-realworld-app#1408. I'm still not sure whether that was a good move or not!

[cacieprins]

@MikeMcC399 Thanks for the comments! This does not make corepack required, it just gives corepack some metadata about which package manager it should be selecting if it is enabled.

[cypress]

cypress    Run #59859

Run Properties:   Passed #59859  •  73b6b546f0: Merge branch 'develop' into add-package-json-packageManager

Project	cypress
Branch Review	add-package-json-packageManager
Run status	Passed #59859
Run duration	18m 09s
Commit	73b6b546f0: Merge branch 'develop' into add-package-json-packageManager
Committer	Cacie Prins
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	6
Pending	1090
Skipped	0
Passing	26419
View all changes introduced in this branch ↗︎

UI Coverage  45.68%
Untested elements	190
Tested elements	164

Accessibility  92.55%
Failed rules	3 critical   8 serious   2 moderate   2 minor
Failed elements	890