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
Under Usage, several mentions are made to corepack checking whether the project is configured for a specific package manager, but no instructions are given for configuring a project for a specific package manager.
It's especially annoying when the project uses pnpm, but hasn't specified it in package.json and corepack assumes the project uses yarn instead, if yarn is also enabled.
It's especially annoying when the project uses pnpm, but hasn't specified it in package.json and corepack assumes the project uses yarn instead, if yarn is also enabled.
Corepack doesn't assume anything like that, if you're seeing otherwise please open a bug report.
Under
Usage
, several mentions are made to corepack checking whether the project is configured for a specific package manager, but no instructions are given for configuring a project for a specific package manager.The yvm deprecation notice and its linked example were the first instruction I found.
The text was updated successfully, but these errors were encountered: