Bump the version of @babel/helper-create-regexp-features-plugin #3363
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
The latest builds fail with the following error (one per each JS pack):
This started happening after upgrading Babel: #3340
The issues seems to be a bug in Babel introduced here. The issue was reported and fixed in v7.21.8.
This version of
@babel/core
was already used in latest porta, but the package@babel/helper-create-regexp-features-plugin
which is the one that has the fix, was still resolved to an older version.This PR just updates the
yarn.lock
file.Generated as follows:
Which issue(s) this PR fixes
-none-
Verification steps
Build the image and make sure the process completes successfully:
Special notes for your reviewer:
@josemigallas had this issue before, but it looked like it was resolved by adding
.browserlistrc
(see https://stackoverflow.com/questions/76162569/babel-error-invalid-version-70001900000/76172109). I think it was probably just a coincidence, as it doesn't seem related.This version bump also upgraded
eslint-plugin-react
from7.31.7
to7.32.2
which added new rules, e.g.react/no-object-type-as-default-prop
, and some issues reported by this rule are also fixed in this PR.https://github.com/jsx-eslint/eslint-plugin-react/blob/master/CHANGELOG.md#added-1