Support Yarn Modern Plug'n'Play (PnP) for CT

[MikeMcC399]

What would you like?

It should be possible to run all Component Testing Supported Frameworks with Yarn Modern in its default Yarn Modern Plug'n'Play (PnP) mode.

If backwards compatibility with earlier versions of Supported Frameworks is not possible, then at least the latest versions of the frameworks should be supported in Yarn PnP mode.

Why is this needed?

Yarn Modern Plug'n'Play is the default mode for new Yarn Modern installations (in which case .yarnrc.yml > nodeLinker is undefined). Setting nodeLinker explicitly to pnp also has the same effect.

Other

This enhancement request is linked to the documentation issue:

• Yarn Modern Plug'n'Play incompatibility with CT missing in docs cypress-documentation#5394

It consolidates and supersedes related issues:

• Cypress config error after CT migration to Yarn Plug'n'Play #26865
• CT dependencies not detected with Yarn Plug'n'Play #26859

It is related also to:

• yarn 2 - cy.readFile does not respect PnP #18072

[cypress-app-bot]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[MikeMcC399]

Please add prevent-stale mark an issue so it is ignored by stale[bot] or reject and close if there is no intention of supporting Yarn Plug'n'Play in Cypress Component Testing.

https://yarnpkg.com/features/pnp

What is Yarn Plug'n'Play?

Yarn Plug'n'Play (generally referred to as Yarn PnP) is the default installation strategy in modern releases of Yarn. It can be swapped out for more traditional approaches (including node_modules installs, or pnpm-style symlink-based approaches), but we recommend it when creating new projects due to its numerous improvements.