search

remy / nodemon

Monitor for any changes in your node.js application and automatically restart the server - perfect for development
http://nodemon.io/
MIT License
26.35k stars 1.74k forks source link

mearn stack #2227

Open manikanta290 opened 2 months ago

manikanta290 commented 2 months ago

nodemon] app crashed waiting for file changes before starting...

[nodemon) restarting due to changes... [nodemon] starting node server.js

(node:15228) [MONGODB DRIVER] Warning: useNewUrlParser is a deprecated option: useNewUrlParser has no effect since Node.js Driver version 4. 0.0 and will be removed in the next major version

(Use node --trace-warnings ... to show where the warning was created)

(node: 15228) [MONGODB DRIVER] Warning: useUnifiedTopology is a deprecated option: useUnifiedTopology has no effect since Node.js Driver vers ion 4.0.0 and will be removed in the next major version

Example app listening on port 3000

MongoDB connection FAIL

[nodemon] app crashed waiting for file changes before starting...

remy commented 2 months ago

What's the actual issue here?

mohit-nagaraj commented 1 month ago

hey idts this is issue from nodemon side rather ur mongo db driver, it does state that useNewUrlParser & useUnifiedTopology is deprecated. dont use them

ravin00 commented 1 month ago

hey idts this is issue from nodemon side rather ur mongo db driver, it does state that useNewUrlParser & useUnifiedTopology is deprecated. dont use them

i agree with it this happened to me too. Since theses are deprecated warnings you can use these below alternatives to overcome the situation.

Set mongoose.set('useNewUrlParser', true) Set mongoose.set('useFindAndModify', false) Set mongoose.set('useCreateIndex', true) Set mongoose.set('useUnifiedTopology', true) Replace update() with updateOne(), updateMany(), or replaceOne() Replace remove() with deleteOne() or deleteMany() Replace count() with countDocuments()

remy commented 1 month ago

So… nothing to do with nodemon?

ravin00 commented 1 month ago

So… nothing to do with nodemon?

I think no this should work

github-actions[bot] commented 2 weeks ago

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up. Thank you for contributing <3