title: Errors when Pushing Vue.js app with IBM Cloud+Cloud Foundry Node Buildpack
body: <p>I am really new (this is my first time) to using IBM Cloud.I have a Vue.js app that I would like to deploy on IBM Cloud with continuous delivery. I have my Vue project in a GitHub repository, and I would like to be able to deploy the project automatically upon changes to the master branch of the repository. I have successfully set up the tool chain so that the "Delivery Pipeline" runs upon changes to the master branch. See screenshot: 
  <a href="https://i.stack.imgur.com/wMG6a.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/wMG6a.png" alt="Tool Chain"></a></p>
  
  <p>Within the Delivery Pipeline, I have two stages: Build and Deploy. See screenshot 2:
  <a href="https://i.stack.imgur.com/jR96V.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/jR96V.png" alt="Delivery Pipeline"></a></p>
  
  <p>I (think) I have successfully set up the Build Stage, where I install npm, then proceed to run the command "npm run build" to create a deployable bundle, with this script:</p>
  
  <pre><code>    bash
      #!/bin/bash
  
      export NODE_VERSION=8
      export NVM_VERSION=0.33.11
  
      npm config delete prefix \
     &amp;&amp; curl -o-
  https://raw.githubusercontent.com/creationix/nvm/v${NVM_VERSION} 
      /install.sh | bash \
    &amp;&amp; export NVM_DIR="$HOME/.nvm" \
    &amp;&amp; . $NVM_DIR/nvm.sh \
    &amp;&amp; nvm install $NODE_VERSION \
    &amp;&amp; nvm alias default $NODE_VERSION \
    &amp;&amp; nvm use default \
    &amp;&amp; node -v \
    &amp;&amp; npm -v
  
  echo "Installing NPM"
  npm install
  echo "NPM install successful"
  echo "Attempting npm run build"
  npm run build
  echo "NPM run build successful"
  </code></pre>
  
  <p><strong>This is where the uncertainty arises.</strong> I want to deploy the project, which after <code>npm run build</code> should just require index.hmtl and build.js, which is in the 'dist' folder.</p>
  
  <p>I don't know if this is necessary, but following the <code>npm install</code> and <code>npm run build</code> stage, I added this stage, which I really don't know what does. I have only added it because the boilerplate SDK for Node.js™
  had this stage prior to the deploy stage, see screenshot 3:
  <a href="https://i.stack.imgur.com/b8xJO.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/b8xJO.png" alt="Simple Build Stage"></a></p>
  
  <p>After this, I have the Deploy stage set to take the 'Simple Build' stage as its input. It deploys it with a simple cloud foundry push command. However, I get these errors in the log, after it downloads the various buildpacks:</p>
  
  <pre><code>Staging...
  -----&gt; IBM SDK for Node.js Buildpack v3.25.1-20190115-1637
         Based on Cloud Foundry Node.js Buildpack v1.5.24
  -----&gt; Creating runtime environment
  
         NPM_CONFIG_LOGLEVEL=error
         NPM_CONFIG_PRODUCTION=true
         NODE_ENV=production
         NODE_MODULES_CACHE=true
  -----&gt; Installing binaries
         engines.node (package.json):  unspecified
         engines.npm (package.json):   unspecified (use default)
  
         Resolving node version (latest stable) via 'node-version-resolver'
         Installing Node.js (6.16.0) from cache
         Using default npm version: 3.10.10
  -----&gt; Restoring cache
         Loading 2 from cacheDirectories (default):
         - node_modules
         - bower_components (not cached - skipping)
  -----&gt; Building dependencies
         Installing node modules (package.json)
  -----&gt; Installing App Management
         WARN: App Management cannot be installed because the start script cannot be found.
         To install App Management utilities, specify your 'node' start script in 'package.json' or 'Procfile'.
  Checking for Dynatrace credentials
  No Dynatrace Service Found (service with substring dynatrace not found in VCAP_SERVICES)
  -----&gt; Caching build
         Clearing previous node cache
         Saving 2 cacheDirectories (default):
         - node_modules
         - bower_components (nothing to cache)
  -----&gt; Build succeeded!
         └── vue@2.6.10
  
   !     This app may not specify any way to start a node process
         http://docs.cloudfoundry.org/buildpacks/node
  Exit status 0
  Staging complete
  Uploading droplet, build artifacts cache...
  Uploading build artifacts cache...
  Uploading droplet...
  Uploaded build artifacts cache (15.3M)
  Uploaded droplet (29.4M)
  Uploading complete
  Stopping instance 64ed3f5f-71eb-477b-afc1-0e07e2e74fdb
  Destroying container
  Successfully destroyed container
  
  0 of 1 instances running, 1 starting
  0 of 1 instances running, 1 starting
  0 of 1 instances running, 1 starting
  0 of 1 instances running, 1 starting
  0 of 1 instances running, 1 starting
  0 of 1 instances running, 1 crashed
  FAILED
  Error restarting application: Start unsuccessful
  </code></pre>
  
  <p>Any ideas? Where am I going wrong? <strong><em>Any help would be greatly appreciated</em></strong>!</p>