-----> Node.js app detected
-----> Creating runtime environment

       NPM_CONFIG_LOGLEVEL=error
       NPM_CONFIG_PRODUCTION=true
       NODE_ENV=staging
       NODE_MODULES_CACHE=true

       npm scripts will see NODE_ENV=production (not 'staging')
       https://docs.npmjs.com/misc/config#production
-----> Installing binaries
       engines.node (package.json):  6.3.1
       engines.npm (package.json):   unspecified (use default)

       Downloading and installing node 6.3.1...
       Using default npm version: 3.10.3
-----> Restoring cache
       Loading 2 from cacheDirectories (default):
       - node_modules
       - bower_components (not cached - skipping)
-----> Building dependencies
       Installing node modules (package.json)
-----> Caching build
       Clearing previous node cache
       Saving 2 cacheDirectories (default):
       - node_modules
       - bower_components (nothing to cache)
-----> Build succeeded!
       ├── dotenv@2.0.0
       ├── lodash@4.16.6
       ├── mongodb@2.2.11
       ├── nested-error-stacks@1.0.1
       ├── nightmare@2.9.1
       ├── nightmare-iframe-manager@0.0.4 (git+https://git@github.com/rosshinkley/nightmare-iframe-manager.git#013f475308e5889c9ee072e19775d0f7d5f9c8e5)
       ├── parse@1.9.1
       ├── pg@6.1.0
       ├── q@1.4.1
       ├── require-env@0.0.4
       ├── rollbar@0.6.2
       ├── sendwithus@2.9.2
       ├── slugid@1.0.3
       └── string-format@0.5.0

 !     This app may not specify any way to start a node process
       https://devcenter.heroku.com/articles/nodejs-support#default-web-process-type
-----> Discovering process types
       Procfile declares types     -> (none)
       Default types for buildpack -> web
-----> Compressing...
       Done: 58.4M
-----> Launching...
       Released v115
       https://is-scheduled-staging.herokuapp.com/ deployed to Heroku