Repository navigation
Corepack should not download package manager if binary is available #586
Description
Is your feature request related to a problem? Please describe.
Yarn has a configuration called yarnPath which allows yarn binary to be added in the repository.
The latest version of yarn, i.e. v4, recommends using corepack instead of yarnPath. However, corepack users do get CI failures sometimes because of network issues when downloading package manager. Example:
In aws-sdk-js-v3, we attempted to use yarnPath to set yarn binary, but we noticed that corepack still attempts to download binary even if it's available. Details in aws/aws-sdk-js-v3#6757 (comment)
A minimal repro can be viewed in https://github.com/trivikr/test-corepack-local-version
Describe the solution you'd like
Corepack should not download package manager if binary is available in the project.
Describe alternatives you've considered
- Following up on existing issues which discuss network failures shared above.
- Use globally installed yarn classic instead of corepack for managing yarn version.
- Switch to
npm@^10.9.0, and use devEngines instead of corepackpackageManagerfield.
Activity
trivikr commentedon Dec 26, 2024
This feature request can be closed based on the following response on OpenJS Slack from one of the maintainers
I agree with corepack maintainer that it shouldn't go through package manager specific configurations.
It's however, an opportunity for https://github.com/openjs-foundation/package-metadata-interoperability-collab-space to check if this configuration can be standardized across package managers.
trivikr commentedon Dec 26, 2024
In aws-sdk-js-v3, we decided to switch from corepack to globally installed yarn classic for using yarn modern local binary as we want to avoid a network call to install package manager.