[Snyk] Security upgrade react-scripts from 1.1.5 to 5.0.0

[saurabharch]

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• fixtures/concurrent/time-slicing/package.json
• fixtures/concurrent/time-slicing/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Use of a Cryptographic Primitive with a Risky Implementation SNYK-JS-ELLIPTIC-14908844	708

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[gemini-code-assist]

Summary of Changes

Hello @saurabharch, 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, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the react-scripts dependency. The update specifically targets and remediates a known cryptographic vulnerability, ensuring more secure application execution.

Highlights

• Dependency Upgrade: The react-scripts dependency has been upgraded from version 1.1.5 to 5.0.0.
• Security Vulnerability Fix: This upgrade addresses a critical vulnerability, "Use of a Cryptographic Primitive with a Risky Implementation" (SNYK-JS-ELLIPTIC-14908844), which had a score of 708.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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 pull request, automatically generated by Snyk, upgrades react-scripts from ^1.1.4 to ^5.0.0 to resolve a security vulnerability. This is a very large jump across multiple major versions (v1 to v5), which introduces significant breaking changes and a high risk of unintended side effects. It's crucial to thoroughly test the application's build, development server, and runtime behavior after this change. Special attention should be paid to compatibility with the experimental React version used in this project, as react-scripts@5 is designed for stable React releases.

[gemini-code-assist]

Upgrading react-scripts from version 1 to 5 is a significant leap that spans multiple major versions. Each major version of react-scripts introduced substantial changes to its underlying dependencies like Webpack, Babel, and Jest.

Some potential issues to watch out for:

• Breaking Changes in Tooling: Webpack 5 (in react-scripts@5) has numerous breaking changes compared to Webpack 3 (in react-scripts@1). This could affect custom build configurations if any exist. Similarly, Jest, Babel, and ESLint have been upgraded significantly.
• Compatibility with Experimental React: This project uses an experimental version of React. react-scripts@5 is tested against stable React versions. There's a risk of incompatibility with the specific experimental features or APIs used here.
• Node.js Version: react-scripts@5 requires Node.js 14 or later. Please ensure your development and CI/CD environments meet this requirement.

Given the high risk of breaking changes, extensive testing of the build, development server, tests, and overall application functionality is strongly recommended.