NodeJs does not start - node.js

Question

Edit: I changed the title for this question because it seemed more accurate.
So this is my package.json file:
{
"name": "application-name",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "node ./bin/www"
},
"dependencies": {
"express": "~4.0.0",
"static-favicon": "~1.0.0",
"morgan": "~1.0.0",
"cookie-parser": "~1.0.1",
"body-parser": "~1.0.0",
"debug": "~0.7.4",
"jade": "~1.3.0",
"mongodb": "*",
"monk": "*"
}
}
I don't really get an error after hitting npm install but it seems like node didn't install all dependencies. Because when we hit the exact same code on my collegue's pc his promt said a lot more feedback on installed dependencies and it worked fine there.
When i now hit "npm start" it just terminates after a few seconds without any response.
I know there is a bug with node at the moment and i already tried to clear my npm chache and adding the "npm update" command and it still doesn't work.
It seems like its a problem with my pc because, like i said, on my collegue's pc everything worked fine. I hope you have any ideas what could be the problem. Thanks a lot in advance!
Edit: Here's what the npm list command gives me:
├─┬ body-parser#1.0.2
│ ├── qs#0.6.6
│ ├─┬ raw-body#1.1.3
│ │ └── bytes#0.2.1
│ └─┬ type-is#1.1.0
│ └── mime#1.2.11
├─┬ cookie-parser#1.0.1
│ ├── cookie#0.1.0
│ └── cookie-signature#1.0.3
├── debug#0.7.4
├─┬ express#4.0.0
│ ├─┬ accepts#1.0.0
│ │ ├── mime#1.2.11
│ │ └── negotiator#0.3.0
│ ├── buffer-crc32#0.2.1
│ ├── cookie#0.1.0
│ ├── cookie-signature#1.0.3
│ ├── debug#0.8.0
│ ├── escape-html#1.0.1
│ ├── fresh#0.2.2
│ ├── merge-descriptors#0.0.2
│ ├── methods#0.1.0
│ ├── parseurl#1.0.1
│ ├── path-to-regexp#0.1.2
│ ├── qs#0.6.6
│ ├── range-parser#1.0.0
│ ├─┬ send#0.2.0
│ │ ├── debug#0.8.0
│ │ └── mime#1.2.11
│ ├─┬ serve-static#1.0.1
│ │ └─┬ send#0.1.4
│ │ ├── debug#0.8.0
│ │ ├── fresh#0.2.0
│ │ ├── mime#1.2.11
│ │ └── range-parser#0.0.4
│ ├─┬ type-is#1.0.0
│ │ └── mime#1.2.11
│ └── utils-merge#1.0.0
├─┬ jade#1.3.1
│ ├── character-parser#1.2.0
│ ├── commander#2.1.0
│ ├─┬ constantinople#2.0.0
│ │ └─┬ uglify-js#2.4.13
│ │ ├── async#0.2.10
│ │ ├─┬ optimist#0.3.7
│ │ │ └── wordwrap#0.0.2
│ │ ├─┬ source-map#0.1.33
│ │ │ └── amdefine#0.1.0
│ │ └── uglify-to-browserify#1.0.2
│ ├── mkdirp#0.3.5
│ ├─┬ monocle#1.1.51
│ │ └─┬ readdirp#0.2.5
│ │ └─┬ minimatch#0.2.14
│ │ ├── lru-cache#2.5.0
│ │ └── sigmund#1.0.0
│ ├─┬ transformers#2.1.0
│ │ ├─┬ css#1.0.8
│ │ │ ├── css-parse#1.0.4
│ │ │ └── css-stringify#1.0.5
│ │ ├─┬ promise#2.0.0
│ │ │ └── is-promise#1.0.0
│ │ └─┬ uglify-js#2.2.5
│ │ ├─┬ optimist#0.3.7
│ │ │ └── wordwrap#0.0.2
│ │ └─┬ source-map#0.1.33
│ │ └── amdefine#0.1.0
│ └─┬ with#3.0.0
│ └─┬ uglify-js#2.4.13
│ ├── async#0.2.10
│ ├─┬ optimist#0.3.7
│ │ └── wordwrap#0.0.2
│ ├─┬ source-map#0.1.33
│ │ └── amdefine#0.1.0
│ └── uglify-to-browserify#1.0.2
├─┬ mongodb#1.4.0
│ ├─┬ bson#0.2.7
│ │ └── nan#0.8.0
│ └── kerberos#0.0.3
├─┬ monk#0.8.1
│ ├── debug#0.8.0
│ ├─┬ mongoskin#0.4.4
│ │ └─┬ mongodb#1.1.11
│ │ └── bson#0.1.5
│ └── mpromise#0.4.4
├─┬ morgan#1.0.0
│ └── bytes#0.2.1
└── static-favicon#1.0.2
So it really looks like the dependencies have been installed (if I'm not completely wrong?). Still my "npm start" command terminates after just a few seconds... any guesses?

Answer 1

If you cleared the npm cache, try also removing all folders in your app's node_modules and run npm install again.
You might want to try starting your app in DEBUG mode and see if it gives you any hint:
DEBUG=express:* node ./bin/www

Answer 2

if the cursor is returning on node app.js(server.js or whatever the name of the js is) like shown below
c:/users/<project-path>:node app.js
c:/users/<project-path>:
Then you might be using express 4 generator
So try the following command
set DEBUG=<project-folder-name>:* & npm start

Answer 3

Not sure if this is resolved or ignored and found a workaround. Just had gone through the problem myself and found out that the problem was not with NodeJS but with one of the dependencies. I failed to install ejs and all my files are ejs based. So I got the same error as you.
So it is best to check if all your dependencies are installed properly.