Fix backend npm install ERESOLVE peer dependency conflict

[Vedhant26]

What changed

• Added a .npmrc file to the backend/ directory.
• Set legacy-peer-deps=true inside .npmrc.

Why

When running npm install in the backend, it fails with an ERESOLVE error because of a peer dependency conflict between mem0ai@2.4.6 and @qdrant/js-client-rest. The mem0ai package enforces strict older peer dependencies.

By adding .npmrc with legacy-peer-deps=true, it resolves the issue by allowing npm to accept an incorrect but functional dependency resolution without breaking the installation process.

How to test

Run the relevant test suite:

�ash id=t1x9ab cd backend npm install

Expected result:

• The installation should complete successfully without any ERESOLVE peer dependency errors.

Screenshots (if UI change)

N/A (Backend/API/Logic change only)

Related issue

Closes #88

---

Pre-Submission Checklist

• Branch named following GSSoC convention: fix/backend-npm-conflict
• Changes committed with meaningful commit message
• Changes pushed to remote fork
• Relevant tests executed successfully
• Code follows project contribution guidelines

[avishek0769]

@Vedhant26 See carefully, your PR includes commits for resolving other issues. Remove those commits of 23rd and 27th May and only keep the relevant commit(s).
Moreover the project uses pnpm not npm so remove the package-lock.json file.

[Vedhant26]

Hi @avishek0769! Thanks for the feedback. I've removed the unrelated commits from the 22nd and 26th of May, and deleted the package-lock.json file since the project uses pnpm. The PR now only contains the specific .npmrc fix for the peer dependency conflict!

[Vedhant26]

Ah, good catch! I've updated the PR description to reflect the pnpm command. Thank you for reviewing!

[avishek0769]

Okay, nice. I will merge it in a few days.