amplify-ui
amplify-ui copied to clipboard
chore(ui-react/v2): adding patched version of babel/traverse
Description of changes
Added babel/traverse 7.23.2
Issue #, if available
Description of how you validated changes
Checklist
- [ ] Have read the Pull Request Guidelines
- [ ] PR description included
- [ ] Relevant documentation is changed or added (and PR referenced)
- [ ]
yarn testpasses and tests are updated/added - [ ] No side effects or
sideEffectsfield updated
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
⚠️ No Changeset found
Latest commit: 19df9abae5af511f31cc9c88928a9746354a9b84
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
Suspect the unit test workflow failure here can be attributed to the example apps pointing to aws-amplify@latest (example). Think we need to audit the versions of Amplify JS we are installing on this branch and make sure that we are not pointing to latest. Not sure exactly which version of aws-amplify will work with the branch, so may require some trial and error to find the correct version supported for this branch. The ESM change is only in aws-amplify@6, so the jest config moduleNameMapper additions should not be required