Seems it can't run against Heruko.

Here is the app log, could you please help to take look?

$ heroku logs --tail
�[36m2014-10-28T07:53:30.477134+00:00 heroku[api]:�[0m Enable Logplex by [email protected]
�[36m2014-10-28T07:53:30.477194+00:00 heroku[api]:�[0m Release v2 created by [email protected]
�[33m2014-10-28T08:00:15+00:00 heroku[slug-compiler]:�[0m Slug compilation started
�[33m2014-10-28T08:00:26+00:00 heroku[slug-compiler]:�[0m Slug compilation finished
�[36m2014-10-28T08:00:26.771740+00:00 heroku[api]:�[0m Scale to web=1 by [email protected]
�[36m2014-10-28T08:00:26.889952+00:00 heroku[api]:�[0m Release v3 created by [email protected]
�[36m2014-10-28T08:00:26.889952+00:00 heroku[api]:�[0m Deploy 76a5f11 by [email protected]
�[32m2014-10-28T08:00:29.049088+00:00 heroku[web.1]:�[0m Starting process with command npm start
�[32m2014-10-28T08:00:30.048318+00:00 app[web.1]:�[0m
�[32m2014-10-28T08:00:30.073308+00:00 app[web.1]:�[0m npm ERR! Exit status 127
�[32m2014-10-28T08:00:30.073071+00:00 app[web.1]:�[0m npm ERR! [email protected] start: server.js
�[32m2014-10-28T08:00:30.073560+00:00 app[web.1]:�[0m npm ERR! Failed at the [email protected] start script.
�[32m2014-10-28T08:00:30.048317+00:00 app[web.1]:�[0m > server.js
�[32m2014-10-28T08:00:30.065031+00:00 app[web.1]:�[0m sh: server.js: not found
�[32m2014-10-28T08:00:30.073449+00:00 app[web.1]:�[0m npm ERR!
�[32m2014-10-28T08:00:30.073918+00:00 app[web.1]:�[0m npm ERR! This is most likely a problem with the zhihudailyfeed pac
kage,
�[32m2014-10-28T08:00:30.048295+00:00 app[web.1]:�[0m
�[32m2014-10-28T08:00:30.048315+00:00 app[web.1]:�[0m > [email protected] start /app
�[32m2014-10-28T08:00:30.074024+00:00 app[web.1]:�[0m npm ERR! not with npm itself.
�[32m2014-10-28T08:00:30.074122+00:00 app[web.1]:�[0m npm ERR! Tell the author that this fails on your system:
�[32m2014-10-28T08:00:30.074436+00:00 app[web.1]:�[0m npm ERR! server.js
�[32m2014-10-28T08:00:30.067449+00:00 app[web.1]:�[0m
�[32m2014-10-28T08:00:30.074832+00:00 app[web.1]:�[0m npm ERR! You can get their info via:
�[32m2014-10-28T08:00:30.075046+00:00 app[web.1]:�[0m npm ERR! There is likely additional logging output above.
�[32m2014-10-28T08:00:30.075186+00:00 app[web.1]:�[0m npm ERR! System Linux 3.8.11-ec2
�[32m2014-10-28T08:00:30.075323+00:00 app[web.1]:�[0m npm ERR! command "/app/vendor/node/bin/node" "/app/vendor/node/bin
/npm" "start"
�[32m2014-10-28T08:00:30.075459+00:00 app[web.1]:�[0m npm ERR! cwd /app
�[32m2014-10-28T08:00:30.075589+00:00 app[web.1]:�[0m npm ERR! node -v v0.10.33
�[32m2014-10-28T08:00:30.075720+00:00 app[web.1]:�[0m npm ERR! npm -v 1.4.28
�[32m2014-10-28T08:00:30.075846+00:00 app[web.1]:�[0m npm ERR! code ELIFECYCLE
�[32m2014-10-28T08:00:30.077608+00:00 app[web.1]:�[0m npm ERR!
�[32m2014-10-28T08:00:30.074942+00:00 app[web.1]:�[0m npm ERR! npm owner ls zhihudailyfeed
�[32m2014-10-28T08:00:30.077720+00:00 app[web.1]:�[0m npm ERR! Additional logging details can be found in:
�[32m2014-10-28T08:00:30.077829+00:00 app[web.1]:�[0m npm ERR! /app/npm-debug.log
�[32m2014-10-28T08:00:30.078022+00:00 app[web.1]:�[0m npm ERR! not ok code 0
�[32m2014-10-28T08:00:30.819805+00:00 heroku[web.1]:�[0m State changed from starting to crashed
�[32m2014-10-28T08:00:30.820581+00:00 heroku[web.1]:�[0m State changed from crashed to starting
�[32m2014-10-28T08:00:30.811109+00:00 heroku[web.1]:�[0m Process exited with status 1
�[32m2014-10-28T08:00:32.327330+00:00 heroku[web.1]:�[0m Starting process with command npm s tart
�[32m2014-10-28T08:00:33.378172+00:00 app[web.1]:�[0m
�[32m2014-10-28T08:00:33.360355+00:00 app[web.1]:�[0m
�[32m2014-10-28T08:00:33.360371+00:00 app[web.1]:�[0m > [email protected] start /app
�[32m2014-10-28T08:00:33.360373+00:00 app[web.1]:�[0m > server.js
�[32m2014-10-28T08:00:33.360374+00:00 app[web.1]:�[0m
�[32m2014-10-28T08:00:33.383931+00:00 app[web.1]:�[0m npm ERR! Failed at the [email protected] start script.
�[32m2014-10-28T08:00:33.384269+00:00 app[web.1]:�[0m npm ERR! This is most likely a problem with the zhihudailyfeed pac
kage,
�[32m2014-10-28T08:00:33.375509+00:00 app[web.1]:�[0m sh: server.js: not found
�[32m2014-10-28T08:00:33.383492+00:00 app[web.1]:�[0m npm ERR! [email protected] start: server.js
�[32m2014-10-28T08:00:33.383689+00:00 app[web.1]:�[0m npm ERR! Exit status 127
�[32m2014-10-28T08:00:33.383824+00:00 app[web.1]:�[0m npm ERR!
�[32m2014-10-28T08:00:33.384364+00:00 app[web.1]:�[0m npm ERR! not with npm itself.
�[32m2014-10-28T08:00:33.384452+00:00 app[web.1]:�[0m npm ERR! Tell the author that this fails on your system:
�[32m2014-10-28T08:00:33.384738+00:00 app[web.1]:�[0m npm ERR! server.js
�[32m2014-10-28T08:00:33.384915+00:00 app[web.1]:�[0m npm ERR! You can get their info via:
�[32m2014-10-28T08:00:33.385243+00:00 app[web.1]:�[0m npm ERR! System Linux 3.8.11-ec2
�[32m2014-10-28T08:00:33.385364+00:00 app[web.1]:�[0m npm ERR! command "/app/vendor/node/bin/node" "/app/vendor/node/bin
/npm" "start"
�[32m2014-10-28T08:00:33.385482+00:00 app[web.1]:�[0m npm ERR! cwd /app
�[32m2014-10-28T08:00:33.385599+00:00 app[web.1]:�[0m npm ERR! node -v v0.10.33
�[32m2014-10-28T08:00:33.385013+00:00 app[web.1]:�[0m npm ERR! npm owner ls zhihudailyfeed
�[32m2014-10-28T08:00:33.385760+00:00 app[web.1]:�[0m npm ERR! npm -v 1.4.28
�[32m2014-10-28T08:00:33.385112+00:00 app[web.1]:�[0m npm ERR! There is likely additional logging output above.
�[32m2014-10-28T08:00:33.385883+00:00 app[web.1]:�[0m npm ERR! code ELIFECYCLE
�[32m2014-10-28T08:00:33.387569+00:00 app[web.1]:�[0m npm ERR! Additional logging details can be found in:
�[32m2014-10-28T08:00:33.387451+00:00 app[web.1]:�[0m npm ERR!
�[32m2014-10-28T08:00:33.387657+00:00 app[web.1]:�[0m npm ERR! /app/npm-debug.log
�[32m2014-10-28T08:00:33.387833+00:00 app[web.1]:�[0m npm ERR! not ok code 0
�[32m2014-10-28T08:00:34.049067+00:00 heroku[web.1]:�[0m State changed from starting to crashed
�[32m2014-10-28T08:00:34.027415+00:00 heroku[web.1]:�[0m Process exited with status 1
�[35m2014-10-28T08:00:35.489494+00:00 heroku[router]:�[0m at=error code=H10 desc="App crashed" method=GET path="/" host=
salty-spire-5447.herokuapp.com request_id=f9d816f2-1985-46db-a23e-8aafc783c86d fwd="54.234.124.84" dyno= connect= servic
e= status=503 bytes=
�[36m2014-10-28T08:00:45.560391+00:00 heroku[api]:�[0m Scale to web=1 by [email protected]
�[35m2014-10-28T08:01:02.775527+00:00 heroku[router]:�[0m at=error code=H10 desc="App crashed" method=GET path="/" host=
salty-spire-5447.herokuapp.com request_id=b3cd7fa7-9aa8-47c0-9a63-7985e194d6b8 fwd="23.226.77.7" dyno= connect= service=
status=503 bytes=
�[35m2014-10-28T08:01:09.709074+00:00 heroku[router]:�[0m at=error code=H10 desc="App crashed" method=GET path="/favicon
.ico" host=salty-spire-5447.herokuapp.com request_id=1afb9c66-54aa-4013-9248-a756421ed76c fwd="23.226.77.7" dyno= connec
t= service= status=503 bytes=