chore: update @uma/* package dependencies
#186
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.
This PR updates some UMA package dependencies. We also need to update the deps in the @across-protocol/sdk-v2 repo after creating a new release of this package. These updates should fix the currently broken
@across-protocol/sdk-v2package that errors with aTypeError:when trying to use it.
I did some digging and it seems to be rooted in conflicting versions of
@uma/contracts-nodeand a breaking change somewhere between the versions 0.2.1 and 0.3.18 of that package. When installing a fresh latest version of the across sdk-v2 package it would install inside the rootnode_modulesSo the old source code of
@uma/sdk v0.23.4would try to use the new code of@uma/contracts-node v0.3.18which are incompatible. Not sure why exactly the version resolution during installation behaves like that but updating the deps to the latest versions should fix the TypeError.