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
corepack was recently deprecated, as no one remaining on the nodejs core team wishes to continue maintaining it (the original author of it and only contributor to it has left the project).
it's also buggy, especially when it comes to pnpm install. I discovered we were using it for this repo when working to automate docs previews for ember-data.
googling tells me I can work around this particular bug by telling corepack to ignore integrity checks entirely if pnpm is in use, but since we also shouldn't be using corepack anymore I figured I'd open an issue.
The text was updated successfully, but these errors were encountered:
so this isn't actually true, corepack is not deprecated they just voted to not include it in the default node installation.
That specific issue that you're seeing is because you don't have a new enough version of corepack installed, just install it globally with either npm i -g corepack or pnpm i -g corepack or whatever you need 👍
@mansona actually I have the latest installed (because I'm using the version that comes via latest node, I don't actually have it installed at all), the issue is that corepack cannot verify any package manager distributed via npm (like pnpm is). Its an open issue, I worked around it by telling it to not verify.
corepack was recently deprecated, as no one remaining on the nodejs core team wishes to continue maintaining it (the original author of it and only contributor to it has left the project).
it's also buggy, especially when it comes to
pnpm install
. I discovered we were using it for this repo when working to automate docs previews forember-data
.googling tells me I can work around this particular bug by telling corepack to ignore integrity checks entirely if pnpm is in use, but since we also shouldn't be using corepack anymore I figured I'd open an issue.
The text was updated successfully, but these errors were encountered: