Node.js – Stopping Heroku from running npm start + what to run instead

bower, gruntjs, heroku, node.js

Disclaimer: I'm a node.js/grunt/bower newbie.

I have a node.js/grunt/bower application that I'm trying to deploy on Heroku. Heroku builds the application as expected, but then it tries to run "npm start" which I did not specify in the package.json file. This command fails, I'm guessing because it is not a server application, and I can not see the actual application deployed in it's place on Heroku. My application can be found here:

So – how do I get Heroku not to run the "npm start" command, and what should it run instead? After running grunt build, the application is available on the dist folder.


{    "name": "sufusku",    "version": "0.0.1",    "description": "Sufusku - makes your annoying sudoku easier",    "repository": {        "type": "git",        "url": "git://"    },    "license": "(MIT OR Apache-2.0)",    "dependencies": {        "bower": "^1.4.1",        "grunt": "0.4.5",        "grunt-cli": "0.1.13",        "grunt-contrib-clean": "^0.6.0",        "grunt-contrib-concat": "^0.5.1",        "grunt-contrib-connect": "^0.11.2",        "grunt-contrib-copy": "^0.8.0",        "grunt-contrib-cssmin": "^0.13.0",        "grunt-contrib-htmlmin": "^0.4.0",        "grunt-contrib-uglify": "^0.9.1",        "grunt-contrib-watch": "^0.6.1",        "grunt-ng-annotate": "^1.0.1",        "load-grunt-config": "^0.17.2",        "time-grunt": "^1.2.1"    },    "devDependencies": {},    "engines": {        "node": ">=0.8.0"    },    "scripts": {        "postinstall": "./node_modules/bower/bin/bower install && grunt build"    }}


module.exports = function (grunt) {    var appname = require('./package.json').name;    require('load-grunt-config')(grunt, {        data: {            dist: 'dist/' + appname,            app: 'src',            distscripts: 'dist/' + appname + '/scripts',            diststyles: 'dist/' + appname + '/styles',            disthtml: 'dist/' + appname,            disttest: 'dist/' + appname + '/test',            appstyles: 'src/css'        }    });    require('time-grunt')(grunt);    grunt.registerTask('build', ['clean:dist', 'ngAnnotate:application', 'uglify', 'htmlmin', 'cssmin', 'copy:serve', 'concat:components']);    grunt.registerTask('serve', ['build', 'connect:livereload', 'watch']);    grunt.registerTask('default', function () {['build']);    });};

Heroku log:

...heroku[web.1]: Starting process with command `npm start`app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"app[web.1]: npm ERR! Linux 3.13.0-57-genericapp[web.1]: npm ERR! npm  v2.11.3app[web.1]: npm ERR! missing script: startapp[web.1]: npm ERR! Please include the following file with any support request: app[web.1]: npm ERR! app[web.1]: npm ERR! node v0.12.7app[web.1]: app[web.1]: npm ERR!     /app/npm-debug.logapp[web.1]: npm ERR! If you need help, you may report this error at:app[web.1]: app[web.1]: npm ERR!     <>heroku[web.1]: Process exited with status 1heroku[web.1]: State changed from starting to crashedheroku[web.1]: State changed from crashed to startingheroku[web.1]: Starting process with command `npm start`app[web.1]: npm ERR! Linux 3.13.0-57-genericapp[web.1]: npm ERR! node v0.12.7app[web.1]: app[web.1]: npm ERR! missing script: start...

Best Solution

npm start is the default web process run when no other process has been specified in a Procfile. Since you say you don't want a server (a web process), the first thing to do is to scale the default process to zero:

heroku scale web=0

Next, you'll want to tell Heroku what process you want to run instead of web by adding its process types to a file called Procfile. For instance, if your app starts with node foobar.js, you could create a Procfile that looks like:

bot: node foobar.js

Then scale the 'bot' process up to at least one:

heroku scale bot=1

Looking at your code above, even though you say it isn't a server-based application, it looks very much like a server-based application. How do you start your app locally? Whatever the answer that should probably go into the Procfile, which you can learn more about here:

disclosure: I'm the Node.js platform owner at Heroku