Skip to content

[Snyk] Upgrade react-scripts from 4.0.1 to 4.0.3 #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4,045 changes: 2,558 additions & 1,487 deletions package-lock.json

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -5,7 +5,7 @@
"dependencies": {
"react": "^17.0.1",
"react-dom": "^17.0.1",
"react-scripts": "4.0.1"
"react-scripts": "4.0.3"

Choose a reason for hiding this comment

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

medium

This upgrade to react-scripts@4.0.3 is a positive and necessary step to address the listed security vulnerabilities.

However, it's important to note that react-scripts version 4.0.3 was released in February 2021, making the 4.x series quite dated. The current stable major version is 5.x, which offers more comprehensive updates and support.

Recommendation for Future Action:
While this PR should be merged to apply these immediate security patches, please consider planning a subsequent upgrade to react-scripts 5.x. Migrating to 5.x will provide:

  • More up-to-date security fixes.
  • Support for newer underlying tools (e.g., Webpack 5, PostCSS 8, ESLint 8).
  • Access to improved features, performance optimizations, and better compatibility with the modern JavaScript ecosystem.

Continuing with react-scripts 4.x long-term may lead to challenges with newer Node.js versions, other dependencies, and potentially leave other vulnerabilities unaddressed.

},
"scripts": {
"start": "react-scripts start"