-
Notifications
You must be signed in to change notification settings - Fork 98
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
deps: update react-scripts to v5.0.0 #350
Conversation
cfe669a
to
ba4f66f
Compare
1132174
to
a10b47c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tACK, just needs a small change in the Docker files.
@@ -1,5 +1,5 @@ | |||
# Start with a NodeJS base image that also contains yarn. | |||
FROM node:12.17.0-buster as nodejsbuilder | |||
FROM node:16.14.2-buster as nodejsbuilder |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also need to bump this version in the Dockerfile
and dev.Dockerfile
, otherwise I get error [email protected]: The engine "node" is incompatible with this module. Expected version ">=14.0.0". Got "12.17.0"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, good catch. I updated those two files in 0233f27
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, LGTM 🎉
This PR updates the
react-scripts
npm dependency along with a few other related packages. I also needed to resolve some breaking changes due to the upgrades ofwebpack
andjest
.Replaces the following PRs:
The dependabot PRs above apply updates to the dependencies of our dependencies by patching the
yarn.lock
file. I typically prefer not to use those because you end up playing a game of wack-a-mole. Once you close one PR, another one pops up shortly afterwards. The better approach is to figure out which top level dependencies need to be updated, and update them. That is what this PR is doing. All of those package updates, plus more, are included in the update toreact-scripts
.To test, you just need to load the site and click around a bit to ensure there are no console errors.