Last pr raised by gupta had issue

[AMANkumar0004]

Reverts #17

Hey @Gupta-02 ,

I’ve reverted the merged PR for now because it was breaking the production deployment.

Here are the issues that occurred after the merge:

1. Cloudinary configuration mismatch

   • Version conflict in multer-storage-cloudinary (v2 vs v4 syntax).
   • Import/export structure mismatch caused CloudinaryStorage is not a constructor.

2. Session configuration issue

   • connect-mongo was throwing Cannot read properties of null (reading 'length').
   • Environment variable (SECRET) was not loading properly.
   • This caused session store crashes.

3. Double response error

   • ERR_HTTP_HEADERS_SENT was occurring due to response being sent more than once in certain flows (error handler + redirect).

Fixes I implemented before reverting:

• Corrected Cloudinary config based on installed version.
• Synced dependency versions properly.
• Fixed session configuration (saveUninitialized: false, proper secret handling).
• Added safe error handler with res.headersSent check.
• Cleaned up duplicate middleware.

However, since the app was still unstable in deployment, I reverted to keep production stable.

I’ll debug everything properly in a separate branch and merge once fully tested.

Thanks for the contribution 🙌

[Gupta-02]

@AMANkumar0004

Yeah when i runned it was working fine the problem was versioning

[AMANkumar0004]

yup it is working fine on the first glance but when you refresh it or do some activity it showing errors on terminals and same while deploying

and pls reimplement the feature we were adding in you Reverts #17 PR