-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mearn stack #2227
Comments
What's the actual issue here? |
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) |
So… nothing to do with nodemon? |
I think no this should work |
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. |
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...
The text was updated successfully, but these errors were encountered: