fix: set web3 version to latest stable #8
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Looks like this is a dependency issue. The dependency we have in this project for svelte web3 needs to add web3 using a CDN which was pointing to
latest. Suprise surprise, some days ago web3 released a major version moving from 1.x.y to 4.x.yThis PR aims to set the web3 version to the latest known stable version, checked in
web.archive.org.Please note that, as of now, the native tokens never resolve, it seems like the IF is doing some maintainance work in the EVM, for if that happens, you can comment out
pollNativeTokensfor testing purposesClose #7