Backwards compatibility with yarn 1.x.x

[saul-atomrigs]

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!

[bang9]

This repository is using yarn@4.2.2. https://github.com/toss/es-toolkit/blob/main/package.json#L16

Would you like to enable corepack and try again?

[saul-atomrigs]

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 😅)
• corepack enable should be documented somewhere, maybe CONTRIBUTING.md or similar. Reference: https://github.com/TanStack/query/blob/main/CONTRIBUTING.md#development

I'm open to add these changes