Thursday, 16 March 2017

Is it okay to use mongoose's mpromise even if it's deprecated?

I am getting the following error when using mongoose with my Node application.

Mongoose: mpromise (mongoose's default promise library) is deprecated, plug in your own promise library instead: http://mongoosejs.com/docs/promises.html

I got many solutions for this from SO and some other sites as well. All says to plug-in some other promise library like native, bluebird etc.

But I could not find anywhere what problem it may cause using mpromise, apart from displaying that warning. Is it okay to ignore the warning and continue using mpromise? Or Should I have to change the promise library? Till now I did not face any problem using that. That's why I am confused about changing the library



via RaR

No comments:

Post a Comment