Skip to content

[Snyk] Security upgrade react-scripts from 3.4.0 to 4.0.0#48

Open
shivpathak-teg wants to merge 1 commit into
masterfrom
snyk-fix-854f73d25ebe0d4bd683a683c3e469c9
Open

[Snyk] Security upgrade react-scripts from 3.4.0 to 4.0.0#48
shivpathak-teg wants to merge 1 commit into
masterfrom
snyk-fix-854f73d25ebe0d4bd683a683c3e469c9

Conversation

@shivpathak-teg

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):

  • example/package.json
  • example/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
medium severity Directory Traversal
SNYK-JS-TAR-15032660
  693  

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:

🦉 Directory Traversal

@shivpathak-teg

Copy link
Copy Markdown
Author

Merge Risk: Medium

This major version upgrade introduces several notable breaking changes by updating underlying tools like ESLint, Jest, and React. It also enables the new JSX Transform by default. While many projects can upgrade without issues, manual changes may be required, especially for projects with customized ESLint configurations or older testing setups.

Highlights:

  • ESLint 7 Upgrade: New linting rules have been added, including for React Testing Library. The EXTEND_ESLINT environment variable is no longer needed for custom configurations.
  • New JSX Transform: Projects no longer need to import React in every file just to use JSX.

Source: Create React App Changelog
Recommendation: After upgrading, delete the node_modules folder and package-lock.json file, then run npm install. Review and update any custom ESLint rules to be compatible with ESLint 7.

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

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