title: JS: nvmrc vs package.json engines?
body: <p>I am trying to lock node and npm version in my javascript project to ensure other developers have those specific versions when building bundles to commit.  I just added this to my package.json: </p>
  
  <pre><code>  "engineStrict" : true,
    "engines": {
      "node" : "10.10.0",
      "npm" : "6.5.0"
    },
  </code></pre>
  
  <p>Will this enforce those versions definitively?  I am unfamiliar with locking down versions since I am used to be the sole developer on frontend projects or inheriting projects that have had this set up.<br>
  Alternatively, is there a benefit of also adding an <code>.nvmrc</code> file that specifies the same version or is that redundant if I'm using engines?</p>