Fix 'Container is falsy' bug due to Babel upgrade #2175
Merged
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.
Description
What we were doing worked, but was broken by Babel's latest patch release; thanks to @nckswt for tracking it down in benjie/ouch-my-finger#16 (comment) and narrowing down that it works fine with
@babel/traverse@7.24.7
but surfaces the error in@babel/traverse@7.24.8
This PR reworks our solution based on the approach outlined in babel/babel#15544 (comment)
Performance impact
Unknown.
Security impact
None known.
Checklist
yarn lint:fix
passes.yarn test
passes.RELEASE_NOTES.md
file (if one exists).