anchor.diff:  
   <strong><%= modified_date %></strong>
   
  +Use the Node.js buildpack with Node or JavaScript apps.
  +
  +You need to install the [Cloud Foundry Command Line Interface (cf CLI)](http://docs-cloudfoundry-staging.cfapps.io/cf-cli/install-go-cli.html) to run some of the commands listed in this topic.
  +
   ## <a id='pushing_apps'></a>Push Node.js Apps ##
   
   Cloud Foundry automatically uses the Node.js buildpack if it detects a `package.json` file in the root directory of your project.
   
  -If your Cloud Foundry deployment does not have the Node.js buildpack installed or the installed version is out of date, you can use the latest version by specifying it with the `-b` option when pushing your application. For example:
  -```bash
  -cf push my_app -b https://github.com/cloudfoundry/buildpack-nodejs.git
  -```
  +The `-b` option lets you specify a buildpack to use with the cf CLI `cf push` command push. If your Cloud Foundry deployment does not have the Node.js buildpack installed or the installed version is out of date, run `cf push APP-NAME -b https://github.com/cloudfoundry/buildpack-nodejs.git` and replace `APP-NAME` with the name of your app to push your app with the latest version of the buildpack. 
  +
  +For example:
  +<pre class='terminal'>
  +$ cf push my-nodejs-app -b https://github.com/cloudfoundry/buildpack-nodejs.git
  +</pre>
   
   For more detailed information about deploying Node.js apps, see the following topics:
   
   * <a href="./node-tips.html" class="subnav">Tips for Node.js Developers</a>
   * <a href="./node-environment.html" class="subnav">Environment Variables Defined by the Node Buildpack</a>
   * <a href="./node-service-bindings.html" class="subnav">Configuring Service Connections for Node</a>
  -
  -You can find the source for the buildpack on GitHub:
  -[https://github.com/cloudfoundry/heroku-buildpack-nodejs](https://github.com/cloudfoundry/heroku-buildpack-nodejs)
  +* <a href="https://github.com/cloudfoundry/heroku-buildpack-nodejs">Node.js Buildpack Source Code on GitHub</a>
   
   ## <a id='supported_versions'></a>Supported Versions ##
   
  -Supported Node versions can be found [in the release notes](https://github.com/cloudfoundry/nodejs-buildpack/releases).
  +For a list of supported Node versions, see the Node.js Buildpack [release notes](https://github.com/cloudfoundry/nodejs-buildpack/releases) on GitHub.
   
  -## <a id='runtime'></a>Specify a Node.js Version##
  +## <a id='runtime'></a>Specify a Node.js Version ##
   
  -Set `engines.node` in `package.json` to the semver range or the specific version of node you are using:
  +To specify a Node.js version, set the `engines.node` in the `package.json` file to the semantic versioning specification (semver) range or the specific version of Node you are using.
  +
  +Example showing a semver range:
   
   ```
   "engines": {
  
positive.code: If you try to use a version that is not currently supported, staging your app fails with the following error message:
  
  <pre class='terminal'>
  $   Could not get translated url, exited with: DEPENDENCY_MISSING_IN_MANIFEST:...
  $   !
  $   !     exit
  $   !
  $   Staging failed: Buildpack compilation step failed
  </pre>
  
  ## <a id='npm_version'></a>Specify an npm Version##
  
  Set `engines.npm` in `package.json` to the semver range or specific version of npm you are using:
  
  ```
  "engines": {
  
negative.code: }
  ```
  
  If you do not specify an npm version, your app uses the default npm packaged with the Node.js version used by your app, as specified on the [Node.js releases](https://nodejs.org/en/download/releases/) page.
  
  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 ##
  
  To vendor dependencies for an app using the Node.js buildpack, run `npm install` from your app directory. This command vendors dependencies into the `node_modules` directory of your app directory.
  
  For example, the following example vendors dependencies into the `my-nodejs-app/node_modules` directory:
  
  <pre class="terminal">
  $ cd my-nodejs-app
  $ npm install 
  </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:
  
  