Turborepo should not enforce setting experimental packageManager

[fabio-colella-md]

Goals

1. packageManager is an experimental property and should not be enforced

Stability: 1 - Experimental. The feature is not subject to semantic versioning rules. Non-backward compatible changes or removal may occur in any future release. Use of the feature is not recommended in production environments.
Experimental features are subdivided into stages:

Non-goals

1. Nothing else than goal 1

Background

packageManager is a property that can optionally be added to a package.json to mandate the version of the package manager to use. This property, as well as Corepack in general is experimental and not recommended for production. However, this property is now required by turborepo since version 2.

Proposal

My proposal is to not enforce this rule in stable releases of turborepo until the feature itself is stable.

[fabio-colella-md]

As a tradeoff, one might set a similar property in the turbo.json file in the root, allowing similar flexibility as for packages, including yarn@* kind of patterns 😊

[anthonyshew]

This configuration option will be a part of 2.0.10: https://github.com/vercel/turbo/releases/tag/v2.0.10-canary.2

[fabio-colella-md]

Wonderful, thanks 🙏 Is this the PR you're referring to? #8738 😊

[anthonyshew]

Yes!