Why is adding a package to the root package.json for in a yarn workspace bad?

I have struggled to find an answer, i just see people constantly say "its bad" with no real reason for why it is bad.Basically my question is like so, we have a bunch of common modules that all packages require (e.g. chai/mocha/typescript). So why is it a bad idea to add it to the root package.json for this library?From my understanding of how hoisting works, they will just end up bubbling up to the top anyways. So wouldn't it be better to globally lock the version of the library across all packages?

Submitted November 01, 2018 at 06:22AM by frankimthetank