he/him 
can we stop with these unactionable warnings for transitive dependencies? > warning jest-expo > jest > jest-cli > jest-config > jest-environment-jsdom > jsdom > left-pad@1.3.0: use String.prototype.padStart() what good does this do the consumer of jest-expo?
Deprecation messages weren't as common pre-Yarn. Capping the depth on which they're displayed is probably the right choice, to either direct dependencies or direct of direct. Pity that npm never offered a mechanism more finegrained. eg. security notices, upgrade notices etc
