-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Compatibility with newer Web3 versions #1690
Comments
This should be expected if one uses a software clearly marked as "beta", right? I honestly wonder what exactly the "many problems" are. I did not encounter any when using truffle. Maybe you can add some links to issues that are caused by using the old version of the web3 beta.37? |
Problems are not caused by the old version ( For now, there is nothing wrong with using that old version, but I opened that issue because Truffle would need to move to a new Web3 version (if not earlier when 1.0 becomes stable). |
Thanks for opening this! |
FWIW this is related web3/web3.js#2266 |
I'm labeling this on hold because the newer Web3.js versions include breaking changes, not only for Web3.js itself, but also for Truffle, since Truffle exposes Web3.js's external interface. These breaking changes will have to wait until Truffle v6. We've identified a path forward; expect an announcement from Web3.js soon! Thanks! |
When will Truffle v6 be released? I know it would be hard, but it is needed. Node.js 12 will become LTS in October, so if it won't be fixed until then, it could be a problem. |
Yes, I will get in a PR for Truffle to use |
It's released! Closing this, as Truffle v5.0.29 now comes with Thanks all! |
How about linking the PR or commit? |
Truffle has many problems with Web3 since
1.0.0-beta.38
.There were many changes in this version including refactoring, porting to ES6 and implementing EthereumProvider. You can see a summary of all changes here. It looks like some of that changes are incompatible with Truffle, so it has many problems.
There was already fix for that (see #1667 and #1689), but it only locked Web3 to
1.0.0-beta.37
which had no problems.This should only be a quick temporary solution because it now uses outdated Web3 version. There should be support for newer versions.
The text was updated successfully, but these errors were encountered: