title: How to force nested npm dependency in package.json
body: <p>I believe this is pretty common question, but still I could not find reliable answer.</p>
  
  <p>In my package.json I have dependency - "grunt-selenium-webdriver", which has some dependency version listed in its package.json  which is not accessible from our network (we are using internal NPM registry which lags sometimes).</p>
  
  <p>I want to use current version of grunt-selenium-webdriver but with different version of nested dependency.
  Is this possible anyhow?</p>
  
  <p>PS: I tried peer dependencies, but it seems that it aims to solve another issue.</p>