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
The documentation states that the known good releases of system wide binaries can be updated using corepack install -g:
Known Good Releases
When running Corepack within projects that don't list a supported package manager, it will default to a set of Known Good Releases.
If there is no Known Good Release for the requested package manager, Corepack looks up the npm registry for the latest available version and cache it for future use.
The Known Good Releases can be updated system-wide using corepack install -g. When Corepack downloads a new version of a given package manager on the same major line as the Known Good Release, it auto-updates it by default.
and
Package managers thus installed will be configured as the new default when calling their respective binaries outside of projects defining the packageManager field.
Yet when I tell corepack to install [email protected] globally, and try to invoke yarn --version it tells me that yarn is using [email protected]. I have cleaned my cache and attempted to install [email protected] globally and then attempt to invoke yarn before the default would get downloaded but I get a prompt telling me to use [email protected].
The text was updated successfully, but these errors were encountered:
The documentation states that the known good releases of system wide binaries can be updated using
corepack install -g
:and
Yet when I tell corepack to install
[email protected]
globally, and try to invokeyarn --version
it tells me that yarn is using[email protected]
. I have cleaned my cache and attempted to install[email protected]
globally and then attempt to invoke yarn before the default would get downloaded but I get a prompt telling me to use[email protected]
.The text was updated successfully, but these errors were encountered: