You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to branch out on this project and do some emailing with nodemailer-react. I discovered that anytime I install any packages on the server side I get a weird warning related to the mongoose package.
Here is the warning I get.
Database connection start (node:17424) [MONGOOSE] DeprecationWarning: Mongoose: thestrictQueryoption will be switched back to falseby default in Mongoose 7. Usemongoose.set('strictQuery', false);if you want to prepare for this change. Or usemongoose.set('strictQuery', true);to suppress this warning. (Usenode --trace-deprecation ...` to show where the warning was created)
Server running on port 5000
`
Not sure why this would happen as I don't get the warning with the package list originally provide in this project.
I wanted to branch out on this project and do some emailing with nodemailer-react. I discovered that anytime I install any packages on the server side I get a weird warning related to the mongoose package.
Here is the warning I get.
Database connection start (node:17424) [MONGOOSE] DeprecationWarning: Mongoose: the
strictQueryoption will be switched back to
falseby default in Mongoose 7. Use
mongoose.set('strictQuery', false);if you want to prepare for this change. Or use
mongoose.set('strictQuery', true);to suppress this warning. (Use
node --trace-deprecation ...` to show where the warning was created)Server running on port 5000
`
Not sure why this would happen as I don't get the warning with the package list originally provide in this project.
My new package list looks like this.
"dependencies": { "body-parser": "^1.19.0", "cors": "^2.8.5", "express": "^4.17.1", "mongoose": "^6.8.1", "nodemailer-react": "^1.0.2", "react": "^16.12.0", "react-dom": "^16.12.0" }
I'm kind of curious what is really going on here.
The text was updated successfully, but these errors were encountered: