Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
MikeMcC399 opened this issue Aug 9, 2024 · 0 comments
Open

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

MikeMcC399 opened this issue Aug 9, 2024 · 0 comments
Labels
CT Issue related to component testing package manager: yarn Issues relating to yarn

Comments

@MikeMcC399
Copy link
Contributor

MikeMcC399 commented Aug 9, 2024

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:

It consolidates and supersedes related issues:

It is related also to:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CT Issue related to component testing package manager: yarn Issues relating to yarn
Projects
None yet
Development

No branches or pull requests

2 participants