arcanis
commented
3 years ago That seems unlikely, unless perhaps you made an overarching workspace glob pattern like ** or similar.
Open ghost opened 3 years ago
arcanis
commented
3 years ago That seems unlikely, unless perhaps you made an overarching workspace glob pattern like ** or similar.
ghost
commented
3 years ago Try it yourself :)
➜ ~ mkdir temp ➜ ~ cd temp ➜ temp yarn init yarn init v1.22.10 question name (temp): question version (1.0.0): question description: question entry point (index.js): question repository url: question author: question license (MIT): question private: success Saved package.json ✨ Done in 2.82s. ➜ temp yarn add clipanion yarn add v1.22.10 info No lockfile found. [1/4] 🔍 Resolving packages... [2/4] 🚚 Fetching packages... [3/4] 🔗 Linking dependencies... warning " > clipanion@3.0.0" has unmet peer dependency "typanion@*". warning Workspaces can only be enabled in private projects. warning Workspaces can only be enabled in private projects. [4/4] 🔨 Building fresh packages...
success Saved lockfile. warning Workspaces can only be enabled in private projects. warning Workspaces can only be enabled in private projects. success Saved 2 new dependencies. info Direct dependencies └─ clipanion@3.0.0 info All dependencies ├─ clipanion@3.0.0 └─ typanion@3.3.2 ✨ Done in 0.39s.
swansontec
commented
3 years ago I am getting the same issue, and the reproduction steps above match my basic setup. This is with Yarn v1.22.17.
Tracked this down to clipanion and typanion. Leaving workspaces in 'package.json' causes yarn to whine, even though they're in
node_modules, which I figured it'd ignore, but noooooooo