Error while installing multer-gridfs-storage along with multer@1.4.5-lts.1

[sudipta9]

Describe the bug

When I tried to install multer-gridfs-storage with the latest lts version of multer, it throws an error

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: project@0.0.0
npm ERR! Found: multer@1.4.5-lts.1
npm ERR! node_modules/multer
npm ERR!   multer@"^1.4.5-lts.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer multer@"^1.4.2" from multer-gridfs-storage@5.0.2
npm ERR! node_modules/multer-gridfs-storage
npm ERR!   multer-gridfs-storage@"*" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/ubuntu/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/ubuntu/.npm/_logs/2022-10-05T05_29_53_065Z-debug-0.log

Environment

• I'm using multer-gridfs-storage version ^5.0.2

• My installed MongoDb version is ^4.9.1

• I have Multer 1.4.5-lts.1 installed to upload files

• The Node version used to run the code is 16.17.1

• I'm using Mongoose connection objects to create storage instances. The Mongoose version installed is ^6.6.3

To Reproduce

• update multer dependency to 1.4.5-lts.1

• Bump multer dependency to 1.4.5-lts.1 #492

Expected behavior

• installing multer-gridfs-storage should not throw any error

[devconcept]

There is a fix on develop but I will not be able to publish until at least one week. I'm having some personal issues right now and that is the cause of the module not being maintained. It will be resolved in a week. I apologize for the inconvenience.

[ujjwalpathaak]

@devconcept hello any update on this issue?

[sudipta9]

@ujjwalpathaak for now try changing the dependency from "multer-gridfs-storage": "^5.0.2" to "multer-gridfs-storage": "github:habur/multer-gridfs-storage”.

Note: this is a temporary solution as of now

Hello guys.
Could you give a rough estimate of when this will be included in the release?
Thank you so much in advance!

[akshittomar]

I am facing the same problem error log is :
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! While resolving: office-boy@0.1.0
npm ERR! Found: multer@1.4.5-lts.1
npm ERR! node_modules/multer
npm ERR! multer@"^1.4.5-lts.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer multer@"^1.4.2" from multer-gridfs-storage@5.0.2
npm ERR! node_modules/multer-gridfs-storage
npm ERR! multer-gridfs-storage@"^5.0.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\HP\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\HP\AppData\Local\npm-cache_logs\2023-03-20T08_20_12_305Z-debug-0.log

[sudipta9]

I am facing the same problem error log is : npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! While resolving: office-boy@0.1.0 npm ERR! Found: multer@1.4.5-lts.1 npm ERR! node_modules/multer npm ERR! multer@"^1.4.5-lts.1" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer multer@"^1.4.2" from multer-gridfs-storage@5.0.2 npm ERR! node_modules/multer-gridfs-storage npm ERR! multer-gridfs-storage@"^5.0.2" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See C:\Users\HP\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\HP\AppData\Local\npm-cache_logs\2023-03-20T08_20_12_305Z-debug-0.log

Try this one
#517 (comment)