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
Hello @bang9 , corepack enable works too, so we have at least two possible solutions!
3 observations to note:
"private": true in package.json works right away, without need to run extra command.
Is it okay to have "private": true? - According to my finding, Yarn Workspaces expect the root package to be private since it only serves as the configuration hub for workspaces, dependencies, etc. so I think it's okay (unless it throws error when publishing 😅)
Hello,
Situation
I forked, cloned and ran
yarn
in the root workspace but I got this error:Solution
It turns out, yarn 1.x.x still requires to have
"private": true
field in the root package.json (https://classic.yarnpkg.com/lang/en/docs/workspaces/#toc-how-to-use-it). Indeed, I added it and successfully installed the dependencies.Proposal
Can I open a pull request with this change? If there's another way, please let me know!
The text was updated successfully, but these errors were encountered: