[Snyk] Upgrade react-router-dom from 5.2.0 to 5.3.4

[nejidevelops]

Snyk has created this PR to upgrade react-router-dom from 5.2.0 to 5.3.4.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 6 versions ahead of your current version.

• The recommended version was released 3 years ago.

Release notes

Package name: react-router-dom

• 5.3.4 - 2022-10-02
• 5.3.3 - 2022-05-18
• 5.3.2 - 2022-05-17
• 5.3.1 - 2022-04-17
• 5.3.0 - 2021-09-03
• 5.2.1 - 2021-08-27
• 5.2.0 - 2020-05-11

from react-router-dom GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• 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 upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[gemini-code-assist]

Summary of Changes

Hello @nejidevelops, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is an automated dependency update initiated by Snyk, aimed at maintaining the project's health and security by upgrading the react-router-dom library to its latest recommended patch version. This ensures the application benefits from the most recent fixes and improvements without introducing breaking changes.

Highlights

• Dependency Upgrade: This pull request upgrades the react-router-dom dependency from version 5.2.0 to 5.3.4.
• Automated Maintenance: The upgrade was automatically generated by Snyk to keep project dependencies up-to-date, which helps in fixing existing vulnerabilities and quickly identifying new ones.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This PR upgrades react-router-dom, which is a good maintenance step. My review includes two main points:

1. A critical issue regarding the missing package lock file (package-lock.json or yarn.lock), which must be added to ensure reproducible builds.
2. A medium severity recommendation to plan a future migration to react-router-dom v6, as v5 is now legacy.

Please address the missing lock file before merging.

[gemini-code-assist]

This PR updates a dependency in package.json, but the corresponding lock file (package-lock.json or yarn.lock) has not been updated and committed with this change.

Lock files are critical for ensuring that every installation of the project uses the exact same dependency versions, leading to reproducible builds across different environments (developer machines, CI/CD, production). Without a lock file, npm install or yarn install might install different versions of transitive dependencies, which can introduce subtle bugs that are hard to track down.

Action Required:
Please run npm install (or yarn install if you are using Yarn) to generate/update the lock file and commit it as part of this pull request.

[gemini-code-assist]

While this upgrade to v5.3.4 is a good step, it's important to note that react-router-dom v5 is now considered legacy. The latest major version is v6, which offers significant advantages:

• A more modern, hooks-based API (useRoutes, useNavigate, etc.)
• Smaller bundle size
• Improved performance and features

I strongly recommend creating a follow-up task to plan the migration from v5 to v6. This will involve breaking changes (e.g., replacing <Switch> with <Routes>), but it's crucial for the long-term health and maintainability of the application.