anchor.diff:  }
   ```
   
  -or
  +Example showing a specific version:
   
   ```
   "engines": {
  
positive.code: }
  ```
  
  If you do not specify an npm version, your app uses the [default npm](https://nodejs.org/en/download/releases/) packaged with your app's Node.js version.
  
  If your environment cannot connect to the Internet and you specified a non-supported version of npm, the buildpack fails to download npm and you see the following error message:
  
  <pre class='terminal'>
  $   We're unable to download the version of npm you've provided (...).
  $   Please remove the npm version specification in package.json (...)
  $   Staging failed: Buildpack compilation step failed
  </pre>
  
  ## <a id='vendoring'></a>Vendor App Dependencies ##
  
  In order to vendor dependencies for an app using the Node.js buildpack, use ```npm```:
  
  <pre class="terminal">
  $ cd APP-DIR
  $ npm install # vendors into APP-DIR/node_modules
  </pre>
  
  The ```cf push``` command uploads the vendored dependencies with the app.
  
  <p class='note'><strong>Note</strong>: For an app to run in a disconnected environment, it must vendor its dependencies.
  For more information, see <a href="https://github.com/cf-buildpacks/buildpack-packager/blob/master/doc/disconnected_environments.md">Disconnected environments</a>.</p>
  
  ## <a id='yarn_disconnected'></a>Using Yarn in a Disconnected Environment ##
  
  Versions 1.5.28 and later of the Node.js buildpack include the ability to use the package manager [Yarn](https://yarnpkg.com/) in a disconnected environment. To do so, you must mirror the Yarn registry locally:
  
  
negative.code: }
  ```
  
  Example showing a specific version:
  
  ```
  "engines": {
  