title: Why is using a dependency of another dependency a bad practice?
body: <p>As the accepted answer in <a href="https://stackoverflow.com/questions/9736514/require-dependency-of-another-dependency-in-node-modules">this question</a> states, the standard practice is to install packages from sub-dependencies that should be used in the app again instead of using it out of the dependencies node_modules folder.</p>
  
  <p>My case is a little different. We have three projects that share the same front end 'core'. To keep the dependencies in sync we install dependencies like slick-slider and node-sass only in our core and access them from our project in which we install the core as a npm dependency.</p>
  
  <p>Are there any downsides beside not seeing the dependency list directly in the project package.json?</p>