Cannot set custom mongoose.Promise when using Typegoose about typegoose

[Omegahorus]

I had some similar Problem with the mongoose. It didn't open the correct connection to the mongo-db and always told me to use not the default mongoose-Promise.

I fixed it with forwarding an existing mongoose model to typegoose.

new User().getModelForClass(User, { existingMongoose: mongoose });

and setting the correct promise (<any>mongoose).Promise = Promise; is only in my main-app file (where I also open the connection).

Hope this solves your problem.

[woxixiulayin]

i got the same issue, that's because in node_modules/typegoose, it has its own mongoose dependence。in your code， mongoose is different from typegoose used from its own dependence.
you can delete the mongoose under node_modules/typegoose/node_modules to solve this.or use typegoose as local module, delete mongoose dependency. and do not put typegoose it in package.json.
this solution is not nice, i hope someone can fix this.
maybe can use moongose as a devDependence or peerDependence

[jakobwilkenson]

Yes, passing through the existing mongoose works! Unfortunately I immediately ran into other issues and decided that the benefit of removing redundancy wasn't worth the cost of having another library with it's own complexities and issues so I removed typegoose.

[EricRabil]

This issue is caused by version conflicts between the version of mongoose that you require and the version of mongoose that typegoose requires. At the time of writing this, typegoose requires [email protected]. Running npm install [email protected] --save or yarn add [email protected] will resolve this issue (note: you may need to clear your node_modules folder after so that the version conflicts are fully resolved)