[Snyk] Fix for 2 vulnerabilities

[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	128
	Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') SNYK-JS-REACTROUTER-18313130	111

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 and react-router-dom v6 to v7 is a major transition that introduces significant architectural changes and new features, moving towards a paradigm similar to the Remix framework. While some changes can be adopted incrementally using future flags, the core update requires substantial code modifications.

Key Breaking Changes & New Concepts:

• Data Routers as Core Paradigm: Version 7 heavily emphasizes "Data Routers" (createBrowserRouter, createHashRouter), which integrate data loading and mutations directly into route definitions using loader and action functions. This is a major shift from the v6 component-based data fetching (e.g., using useEffect).
• Environment Requirements: React Router v7 requires Node.js v20+, React v18+, and react-dom v18+.
• Package Consolidation: The react-router-dom package is being deprecated. Its APIs have been merged into react-router, and imports will need to be updated accordingly. The official changelog for v8 (which finalizes the v7 transition) notes that react-router-dom is removed.
• Route Definition: While component-based routes (<Routes> and <Route>) are still supported, the primary and more powerful way to define routes is now through JavaScript objects passed to the data router creation functions.
• New Hooks and APIs: The introduction of data routers brings new hooks like useLoaderData(), useNavigation(), and useFetcher() for managing data and navigation state.

Recommendation:

This is a high-impact upgrade that requires a significant refactoring effort. It is not a simple version bump. Developers must migrate from component-based data fetching to using loader and action functions on their routes. All package imports from react-router-dom must be changed to react-router. Due to the scale of these changes, it is strongly recommended to handle this migration in a separate, dedicated effort before merging.

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