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
Trying to get all our developers and CI processes to update corepack manually due to #612 is quite painful. It would be nice if corepack had a self-update feature whereby the version of corepack itself could be specified in package.json as well as the package manager version.
Or alternatively if a self-update is not desirable, if we could at least put a constraint like "engines": {"corepack": ">= 0.31.0"} and have corepack exit with an error if that is not met, then that would at least prompt folks to update it themselves.
The text was updated successfully, but these errors were encountered:
Trying to get all our developers and CI processes to update corepack manually due to #612 is quite painful. It would be nice if corepack had a self-update feature whereby the version of corepack itself could be specified in package.json as well as the package manager version.
Or alternatively if a self-update is not desirable, if we could at least put a constraint like
"engines": {"corepack": ">= 0.31.0"}
and have corepack exit with an error if that is not met, then that would at least prompt folks to update it themselves.The text was updated successfully, but these errors were encountered: