search

containerbuildsystem / cachi2

Cachi2 is a CLI tool that pre-fetches your project's dependencies to aid in making your build process network-isolated.
GNU General Public License v3.0
9 stars 27 forks source link

Yarn 1.x: Investigate adding a meta package manager for Yarn #624

Open taylormadore opened 2 months ago

taylormadore commented 2 months ago

Cachi2 users will specify yarn as the package manager or package type for all versions of Yarn. In yarn.lock, the presence of the __metadata field can be used to presume a Yarn v2+ lockfile as can the presence of the string yarn lockfile v1 for a Yarn v1.x lockfile. The request can then be routed to the correct Yarn module in Cachi2.

Implement a PoC for this functionality and file implementation issue(s) as appropriate. It may make sense to delay the implementation until later in the Yarn 1.x development cycle given that we will initially want to have Yarn 1.x as a dev-package-manager.

pavolloffay commented 1 month ago

what is the ETA for yarn 1 support?

We are interested. yarn1 is used by jaeger

eskultety commented 1 month ago

I don't think we've ever had an ETA for package manager work given how big of a task it usually is. The only thing I can tell you is that Yarn v1 is under active heavy development ATM moving forward pretty much every single week, so it's the next big target, so stay tuned, you'll definitely find it in the release notes when it's done.

eskultety commented 1 month ago

what is the ETA for yarn 1 support?

We are interested. yarn1 is used by jaeger

On an unrelated note, @pavolloffay have you considered moving to Yarn v2+? I mean v1 is security maintenance only with the eventual plan to deprecate it completely (I guess they're maintaining it only to give many people enough of a grace period to migrate onto v2+), so while we're adding support for it, it's only to cover the immediate demand for it, but the moment v1 is officially marked as deprecated/unsupported by the Yarn community we'll drop it upstream as well as there's no reason we should keep maintaining support for deprecated stuff in upstream specifically.

pavolloffay commented 1 month ago

we are in process of trying to migrate to yarn 3, but it depends on how much investment it needs from us. That product is deprecated so we don't want to invest a lot into it. It will need to be supported until end of 2025.