Skip to content

[Snyk] Security upgrade react-scripts from 3.4.4 to 4.0.0 - #203

Closed
amplience-snyk wants to merge 1 commit into
masterfrom
snyk-fix-e3ff12387d6a08e621e393ee667d60f9
Closed

[Snyk] Security upgrade react-scripts from 3.4.4 to 4.0.0#203
amplience-snyk wants to merge 1 commit into
masterfrom
snyk-fix-e3ff12387d6a08e621e393ee667d60f9

Conversation

@amplience-snyk

Copy link
Copy Markdown

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/extension/package.json

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.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Inefficient Algorithmic Complexity
SNYK-JS-JSYAML-18313070
  710  

Breaking Change Risk

Merge Risk: High

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:

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

@amplience-snyk

Copy link
Copy Markdown
Author

Merge Risk: High

This is a major version upgrade for react-scripts which introduces significant changes and new features to the build toolchain. While many changes improve the development experience, they can require verification and potentially break existing setups, especially related to testing and linting.

Key Breaking Changes:

  • Jest 26 Upgrade: react-scripts now uses Jest 26, up from version 24. A significant change is that resetMocks is now enabled by default. This can break tests that rely on mock states persisting between tests within the same file.
  • ESLint 7 Upgrade: Upgrades to ESLint 7 and adds new rules. This may cause new linting errors in your project. The EXTEND_ESLINT environment variable is no longer needed for custom configurations.
  • Fast Refresh: Replaces the old React Hot Loader. While it offers a better experience by preserving component state, this is a significant change to the development server's behavior.
  • React 17 Support: Includes support for React 17 and its new JSX Transform, which means import React from 'react' is no longer required in component files to use JSX.
  • Dependency Updates: Includes updates for TypeScript 4, react-testing-library, and PWA workbox improvements.

Recommendation:

Due to the automatic mock resets in Jest and new ESLint rules, this upgrade is considered high risk. It is critical to run your entire test suite after upgrading. If tests fail due to mock issues, you may need to adjust them or disable the new default behavior by setting "jest": { "resetMocks": false } in your package.json. Also, review any new ESLint errors. The official advice is to delete your node_modules folder and reinstall dependencies if you encounter errors.

Source: Create React App 4.0 Release Notes

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

@amplience-snyk

amplience-snyk commented Jul 27, 2026

Copy link
Copy Markdown
Author

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@orca-security-eu orca-security-eu Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Orca Security Scan Summary

Status Check Issues by priority
Passed Passed Infrastructure as Code high 0   medium 0   low 0   info 0 View in Orca
Passed Passed SAST high 0   medium 0   low 0   info 0 View in Orca
Passed Passed Secrets high 0   medium 0   low 0   info 0 View in Orca
Passed Passed Vulnerabilities high 0   medium 0   low 0   info 0 View in Orca

@amplience-snyk

Copy link
Copy Markdown
Author

✅ This PR has been automatically closed

The security issues addressed by this pull request are no longer present in the latest project scan. All vulnerabilities this PR was created to fix have been resolved through other means (e.g., dependency updates, direct fixes, or changes in vulnerability data).

Resolved Issues

  • SNYK-JS-JSYAML-18313070

What should I do?

No action is required. If you believe this PR was closed in error, you can reopen it and contact Snyk support.


This action was performed automatically by Snyk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants