anchor.diff:  owner: Buildpacks
   ---
   
  -This topic describes how to install the Node.js Cloud Native Buildpack (CNB).
  -### Install Processes:
  +This topic describes how to prepare your Node or JavaScript apps to use the Node.js Cloud Native Buildpack (CNB)
  +instead of the Cloud Foundry-only Node.js buildpack.
  +
  +
  +##<a id='install-processes'></a> Install Processes:
   With the new Node.js Cloud Native Buildpack, the installation commands
  -that we choose to build an applications `node_modules` have changed
  +that we choose to build an apps `node_modules` have changed
   as follows:
   
     - We assume that all of the following are updated and in agreement
  -    before an application is `cf pushed`
  +    before an app is `cf pushed`
       - `package.json`
       - `package-lock.json` (optional)
       - `node_modules` (optional)
  
positive.code: include certain external integration helpers, such as those for APM agents.
  </p>
  
  ### Buildpack ordering
  The compatibility layer generated by `cnb2cf` imposes some additional
  constraints on multi-buildpacks builds.  If a CF-compatible CNB is used during
  multibuildpack builds. All subsequent buildpacks must also be CF-compatible CNB.
  In the example `cf push` below all buildpacks between
  `compat-cn_buildpack_1` and `compat-cn_buildpack_n` must be a CF-compatible CNB.
  
  
negative.code: 
  
  As a result we require that apps that contain `node_modules` or `npm-cache` must contain
  all of the dependencies required for a successful `npm` or `yarn` install.
  
  For additional details on how the installation process is chosen of this buildpack see
  [ Node.js Cloud Native Buildpack installation process](../nodejs-cnb#npm-installation-process).
  