`packageManager` should accept a version range

nodejs / corepack

Zero-runtime-dependency package acting as bridge between Node projects and their package managers

MIT License

2.31k stars 146 forks source link

`packageManager` should accept a version range #404

Closed GeoffreyBooth closed 4 months ago

GeoffreyBooth commented 4 months ago

Just as engines supports values like >= 10.0.0, I should be able to tell Corepack that I want a particular version range rather than only being allowed to pin a precise version.

Split off from #402.

aduh95 commented 4 months ago

Duplicate of https://github.com/nodejs/corepack/issues/95