AUTO_PIN should not change to different package manager

[MikeMcC399]

What would you like?

Corepack AUTO_PIN should not attempt to automatically change to a different package manager in a project, such as attempting to change an npm project into a Yarn project.

Why is this needed?

By default, and if the environment variable COREPACK_ENABLE_AUTO_PIN is not set to 0, then Corepack adds a packageManager field to an existing package.json file if the field is not present.

If a project is identifiable through a lock file

Lock file	Package Manager
package-lock.json	npm
pnpm-lock.yaml	pnpm
yarn.lock	Yarn Classic
yarn.lock	Yarn Modern

then AUTO_PIN should not attempt to add a packageManager field for a different package manager.

Other

• related to Prompt before applying AUTO_PIN to package.json #691

[MikeMcC399]

This issue is now less critical, since the merge of #709 and the release of corepack@0.33.0