anchor.diff:  }
   ```
   
  -or
  +Example showing a specific version:
   
   ```
   "engines": {
  
positive.code: }
  ```
  
  or
  
  ```
  "engines": {
  
negative.code: 
  <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.
  
  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>
  * <a href="https://github.com/cloudfoundry/heroku-buildpack-nodejs">Node.js Buildpack Source Code on GitHub</a>
  
  ## <a id='supported_versions'></a>Supported Versions ##
  
  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 ##
  
  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": {
  