You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently npm is installed as a bi-effect of downloading node. This assumption is fine as long npm is the package manager of choice, and the user doesn't much care which npm version they use.
Describe the solution you'd like node distributions now ship with corepack, a wrapper script for managing package manager versions. Pants should use
this script to install the package manager version users request. Corepack ships with good features, such as a "good known release" list which pants can rely on. Describe alternatives you've considered
Manage package managers in pants via template tool downloads or sandboxing npm installations. Essentially re-invent the wheel.
Additional context
🤷♂️
The text was updated successfully, but these errors were encountered:
Enables users to configure a wanted version of a package manager blessed
by Corepack, either by:
1. Setting a package manager version in the nodejs subsystem; or
2. Placing a `packageManager` entry in their `package.json`, the feature
of Corepack.
This is a prerequisite for pnpm and yarn support.
Fixes#18525.
Is your feature request related to a problem? Please describe.
Currently
npm
is installed as a bi-effect of downloadingnode
. This assumption is fine as long npm is the package manager of choice, and the user doesn't much care which npm version they use.Describe the solution you'd like
node
distributions now ship withcorepack
, a wrapper script for managing package manager versions. Pants should usethis script to install the package manager version users request. Corepack ships with good features, such as a "good known release" list which pants can rely on.
Describe alternatives you've considered
Manage package managers in pants via template tool downloads or sandboxing
npm
installations. Essentially re-invent the wheel.Additional context
🤷♂️
The text was updated successfully, but these errors were encountered: