removing node_modules from backend and updated .gitignore and CustomerReview Section Fix#216
removing node_modules from backend and updated .gitignore and CustomerReview Section Fix#216ayushpandey101 wants to merge 0 commit into
Conversation
Thanks for creating a PR for your Issue!
|
|
Hi @Skrishna0703, I’ve removed the I've also included the changes of the other issue #206 with the issue #204 so that there is no git conflict issue while merging it to your codebase. This change improves repository hygiene and streamlines collaboration for all contributors while also improving the Thanks! |

Which issue does this PR close?
Rationale for this change
The
node_modulesfolder in the backend was not included in.gitignore, causing unnecessary Git tracking of dependency files. This leads to:By removing
node_modulesfrom version control and adding it to.gitignore, we ensure:✅ Cleaner commits
✅ Smaller repo size
✅ Consistent dependency installation via
package.json+npm install✅ Better team collaboration & Git hygiene
2nd issue resolved the Review-Content-Card Overflow
✅ Cleaner UI
✅ Arrow Changed
✅ Added Glow to swriper-btn
What changes are included in this PR?
Removed existing
node_modules/folder from Git tracking (if previously committed)Added
/node_modules/to.gitignorein the backend root directoryVerified no other critical ignores were missing (optional: added common ones like
.env,*.logif not present)2nd issue changes include:
Are these changes tested?
✅ Yes — manually verified:
git status→ confirmsnode_modules/is no longer trackednpm install→ confirmed dependencies install correctly.gitignoresyntax — valid and workingAre there any user-facing changes?
🚫 No.
This is a developer/Git workflow improvement. End users or app functionality are unaffected.
Screenshots (if Aplicable)
For issue #204
📸 Not applicable — this is a backend/Git configuration change with no UI impact.
For issue #206

Dark mode:
Light mode:

✅ Ready to merge.
Improves codebase maintainability and prevents future Git headaches.