-
Notifications
You must be signed in to change notification settings - Fork 465
general - Unable to use 0x libraries: 'cannot read property slice of undefined' #2041
Comments
I'm experiencing the same exact issue. |
Thanks for the report @the-jackalope @DonGambas. I just tried to reproducing the issue on the latest release, and it works as expected:
Since this was a major version bump for the library and introduced quite a big change to the public interface, we put together this upgrade guide: #2040 |
@fabioberger thanks for the response, I initially installed the packaged with npm, when I installed them with yarn there was no issue 🤦♂ I have one additional question re: the upgrade guide. All of the order validation functions got moved to the order-utils package. It would be helpful to see an example of how to use the order validation utils in the order-utils package in particular how to set up the |
@DonGambas glad you were able to get that sorted. Which order validation method are you using and what precisely is your use-case? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because no activity occured in 7 days after being marked as stale. If it's still relevant - feel free to reopen. Thank you for your contributions. |
Doing almost anything that makes requests to the network with the latest release of various 0x libraries results in the same error. The easiest to demonstrate is the
contract-wrappers
repo - I expect to retrieve a public address's ZRX token balance on the mainnet with the following code:Which consistently yield the following error:
Whereas I expect to get the address's token balance. I don't believe it to be an issue with the provider as I can instantiate a Web3 instance with the provider and use it to correctly query the address's ETH balance.
@0x/contract-wrappers:
10.1.0
web3:
1.0.0-beta.55
The text was updated successfully, but these errors were encountered: