[Snyk] Security upgrade react-router-dom from 6.30.4 to 7.18.0

[riddhi-desai]

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Open Redirect SNYK-JS-REACTROUTER-18313144	129
	Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') SNYK-JS-REACTROUTER-18313130	112

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Open Redirect

[riddhi-desai]

The upgrade from react-router-dom v6 to v7 is a major version change that introduces significant architectural shifts and breaking changes. While the React Router team has provided an incremental migration path using 'future flags' in late v6 versions, this upgrade requires careful planning and likely code modifications.

Key Breaking Changes & Considerations:

• Environment Requirements: v7 requires Node.js v20+, React v18+, and react-dom v18+ to be used.
• Data Router Paradigm: v7 fully embraces the "Data Router" paradigm (using createBrowserRouter). If your application is still using <BrowserRouter>, you will need to migrate to createBrowserRouter to leverage the new data fetching and mutation APIs.
• Loaders and Actions: Data loader and action functions must now return Response objects. Returning plain JavaScript objects is no longer supported. You can use the json() utility from react-router-dom to create these responses.
• Future Flags: The recommended migration path is to enable future flags in your v6 application to opt into v7 behaviors incrementally before upgrading the version number.
• Package Structure: While react-router-dom is still used, the library is moving towards a consolidated react-router package. Be prepared to update imports in the future, as DOM-specific APIs will eventually live in react-router/dom.

Recommendation:
This is a high-impact upgrade. Before merging, developers must:

1. Verify the application meets the Node.js and React version prerequisites.
2. Follow the official migration guide, adopting the future flags in v6 to address breaking changes one by one.
3. Refactor all loader and action functions to return Response objects.
4. Thoroughly test all routing, data loading, and form submission logic after the upgrade.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[codacy-production]

Not up to standards ⛔

🔴 Issues 1 high

Alerts:
⚠ 1 issue (≤ 0 issues of at least minor severity)

Results:
1 new issue

Category	Results
Security	1 high

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}