chore: audit and pin exact dependency versions in comebackhere-frontend/package.json and frontend/package.json

[misrasamuelisiguzor-oss]

Description

With two separate React frontends and their own package-lock.json files, dependency version drift between the two (e.g. different React or Vite major versions) could cause inconsistent behavior or bugs that only reproduce in one app. An audit would catch avoidable drift.

This is repository-level tooling, configuration, or process rather than application code, but that doesn't make it lower stakes: onboarding friction, unclear ownership, and process gaps are consistently what determines whether a project with this much surface area (two contract trees, two backend trees, two frontend apps, a static dashboard, and an active external contributor program) stays maintainable as it grows or slowly accumulates inconsistency that nobody has the full context to untangle.

Given that this repository is actively recruiting outside contributors through the Stellar Wave bounty program (this issue included), the quality of its repository-level scaffolding, from CONTRIBUTING.md to CODEOWNERS to its issue and PR templates, has a direct and measurable effect on how many contributors are able to land a change successfully on their first attempt versus giving up in the setup phase.

Requirements and context

• Compare shared dependencies (React, Vite, TypeScript, testing libs) across both package.json files and align versions where there's no reason to differ

Suggested execution

1. Fork the repo and create a branch

   git checkout -b chore/frontend-dependency-version-audit
   

2. Implement changes

• Update comebackhere-frontend/package.json and frontend/package.json as needed

3. Test and commit

• Run each app's build and test suite after alignment

Example commit message

chore: align shared dependency versions across both frontend apps

Guidelines

• Assignment required before starting
• PR description must include: Closes #[issue_id]
• Keep PR description professional and detailed

[amiramusa187-glitch]

@amiramusa187-glitch has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, can I work on this please?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @amiramusa187-glitch to this issue.

[precious1joe]

@precious1joe has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

i would like to work on this issue kindly assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @precious1joe to this issue.

[kwest0002-lab]

@kwest0002-lab has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

please i will love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @kwest0002-lab to this issue.

[Bidex-cmyk]

@baedboibidex-cmyk has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

i would love to work on this issue pls assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @baedboibidex-cmyk to this issue.

[drips-wave]

Congratulations, @kwest0002-lab! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @kwest0002-lab: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊