Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Update to Mongoose v6 and MongoDB v4
See original GitHub issueFirst I want to thank you for this wonderful package.
Do you know when this project will be updated to use Mongoose v6 and MongoDB v4? I see that PRs for these issues are already open: https://github.com/devconcept/multer-gridfs-storage/pull/375 https://github.com/devconcept/multer-gridfs-storage/pull/376
I have a project that relies on both multer-gridfs-storage and mongoose, and I can’t update to mongoose v6 until this package is updated due to type conflicts.
Describe your problem
Environment
Additional context
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
A fix has been released v5.0.2. Please confirm that it works to close this issue.
I see now. Is not that mongoose is incompatible, is that by not providing the client parameter the module assumes version 2.2 of mongodb. This is an easy fix and dealing with the error is the wrong approach since the module deals with behavior from versions 2.2, 3 and 4 and also the lack of parameters provided by the consumer of the module will make it unreliable. I will provide a fix on the next few days.