can't use `yarn add` on non-private workspaces

yarnpkg / yarn

The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry

https://classic.yarnpkg.com

Other

41.4k stars 2.72k forks source link

can't use `yarn add` on non-private workspaces #6506

Open bluelovers opened 5 years ago

bluelovers commented 5 years ago

Do you want to request a feature or report a bug?

hope can have a option for allow Workspaces use on non-private projects

What is the current behavior?

$ yarn add xxxx
Workspaces can only be enabled in private projects.

What is the expected behavior?

a options let user can choose force enable it

Please mention your node.js, yarn and operating system version.

dword-design commented 4 years ago

Hey, I wanna bump this up. I think there are use cases where it makes sense to have workspaces in public packages. I'm using workspaces for Nuxt modules and since Nuxt in the end builds its files via Webpack, the workspaces aren't in fact published but only the built files. The workspaces aren't actually published packages in this case.