Upgrading to the latest nodemon, fails to start the application: "clean exit - waiting for changes before restart".
Reverting to 1.2.1 fixed the problem so our applications could start.
Are you able to provide any actual details about what the issue is? Ideally
a way to easily replicate.
On 20 Jan 2015 17:50, "Kevin Malakoff" [email protected] wrote:
Upgrading to the latest nodemon, fails to start the application: "clean
exit - waiting for changes before restart".Reverting to 1.2.1 fixed the problem so our applications could start.
—
Reply to this email directly or view it on GitHub
https://github.com/remy/nodemon/issues/472.
Closing due to inactivity... Happy to open again if there's information about the actual issue.
The same thing is happening with me too. It is happening for a file which is using express. There is another file, residing in the same directory which I can still run through nodemon.
in package.json
"scripts":{
// "start": "node ./bin/www"
"start": "nodemon ./bin/www"
}
the following would now be equivalent:
$ npm start
$ nodemon ./bin/www
Same thing is happening to me with express 4.12.2, nodemon v1.3.7
Simple run nodemon without any arguments or run nodemon bin/www.
I had the same problem and I had just forgotten to export MONGO_URL to my mongodb user
let db = await MongoClient.connect(process.env.MONGO_URL);
in my server.js required
export MONGO_URL=mongodb://{user}:{password}@ds055555.mongolab.com:55555/{project}
if you using express-generator, you have to start your app with ./bin/www not app.js
I have faced this problem too. I realize that mongo.connect() has problems, so nodemon exits completely. The problem can be found using via
mongo.connect(url,{}, function(err){
if(err)console.log(err);
});
for me simply npm clean-install worked
Most helpful comment
Simple run
nodemonwithout any arguments or runnodemon bin/www.