The caveats are interesting as I don't think I've encountered this issue with Yarn Workspaces. In my experience yarn workspaces doesn't hoist and flatten node_

The caveats are interesting as I don't think I've encountered this issue with Yarn Workspaces. In my experience yarn workspaces doesn't hoist and flatten node_modules, it tends to hoist the popular version and leaves variances next to that particular workspace e.g. library A and B rely on Typescript 1.0, but library C relies on Typescript 2.0, then Typescript 1.0 will be in root node_modules, while Typescript 2.0 will be in libraryC/node_modules. It also lets you run `yarn workspaces focus`, so it only installs the node_modules that libraryA needs for example. So the atomic deployments caveat in the article shouldn't be an issue. I'm surprised NPM workspaces doesn't do this.